oauth2 rfc6749 requires TLS for authorization endpoint #1917
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
Signed-off-by: Axel Nennker <axel.nennker@telekom.de>
|
Thanks for the PR. As v3.0.2 is released, changes should go against the most recent patch version on the associated You will see that a number of these changes have already been made in v3.0.3. As to the meat of this change, I think we should note what users of the specification MUST do, and not what components of the oAuth dance MUST do, to make it clear we are not intending to make changes to the referenced RFC behaviour. I.e. something like "The authorization URL must specify a secure scheme" rather than "The authorization server MUST require the use of TLS." |
* Fix missing schema type in YAML example spec * Moved type: object into allOf
|
Closing this as it is not based on the latest -dev branch. |
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.
Signed-off-by: Axel Nennker axel.nennker@telekom.de
Referencing OAuth2 Authorization Endpoint
Since requests to the authorization endpoint result in user authentication and the transmission of clear-text credentials (in the HTTP response), the authorization server MUST require the use of TLS as described in Section 1.6 when sending requests to the authorization endpoint.Changed the other http URLs to https as well because 'confidentiality' e.g. user information in some examples