Separate headers for sensitive values (orgKey) in registerCluster response #1331
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… sensitive values as separate headers object in addition to in the url query params. Using the url alone, with included authorization value (orgKey) is still possible, but now deprecated. A future major release will make the breaking change that removes the query parameter from the URL and require use of the headers returned separately for authorized requests. The use of headers for sensitive values (e.g. authorization values) will improve security.
carrolp
changed the title
kdai7
approved these changes
Jun 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cluster registration, deletion, and enableRegistrationUrl apis now return sensitive values as separate headers object in addition to in the url query params.
Using the url alone, with included authorization value (orgKey) is still possible, but now deprecated. A future major release will make the breaking change that removes the query parameter from the URL and require use of the headers returned separately for authorized requests. The use of headers for sensitive values (e.g. authorization values) will improve security.