Skip to content

Add registration secret as header in node responses - #8661

Merged
AutomatedTester merged 4 commits into
SeleniumHQ:trunkfrom
raju249:registration-secret
Sep 24, 2020
Merged

Add registration secret as header in node responses#8661
AutomatedTester merged 4 commits into
SeleniumHQ:trunkfrom
raju249:registration-secret

Conversation

@raju249

@raju249 raju249 commented Sep 1, 2020

Copy link
Copy Markdown
Member

Thanks for contributing to Selenium!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

Fixes #8559

Motivation and Context

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have read the contributing document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@raju249

raju249 commented Sep 1, 2020

Copy link
Copy Markdown
Member Author

@adamgoucher Do you mind taking a look at my start for fixing #8559 ?

I am trying to find the places where the header will be validated. If possible, please point some files here, where the header should be validated :)

@raju249
raju249 marked this pull request as ready for review September 3, 2020 09:52
@AutomatedTester

Copy link
Copy Markdown
Member

There are linting errors, please fix those

@raju249
raju249 force-pushed the registration-secret branch 2 times, most recently from bb90fff to 6b91b4d Compare September 7, 2020 09:40
@raju249
raju249 requested a review from adamgoucher September 7, 2020 09:58
@raju249

raju249 commented Sep 7, 2020

Copy link
Copy Markdown
Member Author

@adamgoucher Do you mind reviewing/approving this PR? 🙇

@diemol diemol left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How can I test this? 🤔

@adamgoucher

Copy link
Copy Markdown
Contributor

My theory for how to test this is

  • start a hub with https and registration secret
  • start a node with the registration secret
  • run a test through the node
  • restart the node with the registration secret (while maybe blackhole-omg the traffic so it doesn’t try to re-register with the hub)
  • try to send another another job to the node

The theory is that the hub would send a message and the node would reply without the header present and the hub would no longer trust the node and pull it out of the pool, not send commands, etc.

@raju249
raju249 force-pushed the registration-secret branch from 974e194 to 6389a52 Compare September 24, 2020 09:57
@raju249

raju249 commented Sep 24, 2020

Copy link
Copy Markdown
Member Author

I have fixed the conflicts.

@AutomatedTester
AutomatedTester merged commit 7c7e296 into SeleniumHQ:trunk Sep 24, 2020
@raju249
raju249 deleted the registration-secret branch September 28, 2020 06:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Send registration-secret via header for web calls

4 participants