SAML 2.0 Bearer flow as alternative to Authorization Code flow#5412
Draft
HeikoTheissen wants to merge 2 commits into
Draft
SAML 2.0 Bearer flow as alternative to Authorization Code flow#5412HeikoTheissen wants to merge 2 commits into
HeikoTheissen wants to merge 2 commits into
Conversation
HeikoTheissen
commented
Jul 2, 2026
| | <a name="oauth-flow-authorization-url"></a>authorizationUrl | `string` | `oauth2` (`"implicit"`, `"authorizationCode"`) | **REQUIRED**. The authorization URL to be used for this flow. This MUST be in the form of a URL. The OAuth2 standard requires the use of TLS. | | ||
| | <a name="oauth-flow-device-authorization-url"></a>deviceAuthorizationUrl | `string` | `oauth2` (`"deviceAuthorization"`) | **REQUIRED**. The device authorization URL to be used for this flow. This MUST be in the form of a URL. The OAuth2 standard requires the use of TLS. | | ||
| | <a name="oauth-flow-token-url"></a>tokenUrl | `string` | `oauth2` (`"password"`, `"clientCredentials"`, `"authorizationCode"`, `"deviceAuthorization"`) | **REQUIRED**. The token URL to be used for this flow. This MUST be in the form of a URL. The OAuth2 standard requires the use of TLS. | | ||
| | <a name="oauth-flow-samlmetadata-url"></a>samlMetadataUrl | `string` | `oauth2` (`"saml2Bearer"`) | The metadata URL for the SAML entity that accepts the SAML assertion. This MUST be in the form of a URL. | |
Author
There was a problem hiding this comment.
Does it make sense to advertise this? Other meta-information (like where to register a new OAuth client) are not advertised here either.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
SAML 2.0 Bearer flow is an OAuth authentication flow with principal propagation which, unlike Authorization Code flow, does not prompt the user for consent. It is typically used for integration between business systems where trust has been set up centrally by administrators and individual users (employees) need not consent.
This pull request introduces SAML 2.0 Bearer flow as a new option into the OpenAPI Security Scheme Object.