coexistence with bearer tokens #84
Open
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
yaronf
requested changes
Dec 23, 2024
| The WIT and WPT define new HTTP headers. They can therefore be presented along with existing headers used for JWT bearer tokens. This | ||
| property allows for transition from mechanisms using identity tokens based on bearer JWTs to proof of possession based WITs. | ||
| A workload may implement a policy that accepts both bearer tokens and WITs during a transition period. This policy may be configurable | ||
| per-caller to allow the workload reject bearer tokens from callers that support WITs. Once a deployment fully supports WITs, then the use of |
There was a problem hiding this comment.
Suggested change
| per-caller to allow the workload reject bearer tokens from callers that support WITs. Once a deployment fully supports WITs, then the use of | |
| per-caller to allow the workload to reject bearer tokens from callers that support WITs. Once a deployment fully supports WITs, then the use of |
There was a problem hiding this comment.
Suggest to add: Implementations should be careful when implementing such a transition strategy, since the decision which token to prefer is made when the caller's identity has still not been authenticated, and needs to be revalidated following the authentication step.
| authorization policy may take into account both the sending workload's identity and the information in the context token. For example, the | ||
| identity in the WIT may be used to establish which API calls can be made and information in the context token may be used to determine | ||
| which specific resources can be accessed. | ||
|
|
There was a problem hiding this comment.
This is OK for now, but I think eventually we will want one subsection for coexistence with legacy stuff and another for authorization.
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.
Resolve with Issue #53