Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This PR removes a mention of refresh tokens. #20

Merged
merged 1 commit into from
Jul 8, 2024
Merged

Conversation

adeinega
Copy link
Collaborator

@adeinega adeinega commented Jul 7, 2024

RFC8693 does allow to get a RT in some cases but does not take / exchange it.

A refresh token will typically not be issued when the exchange is of one temporary credential (the subject_token) for a different temporary credential (the issued token) for use in some other context. A refresh token can be issued in cases where the client of the token exchange needs the ability to access a resource even when the original credential is no longer valid (e.g., user-not-present or offline scenarios where there is no longer any user entertaining an active session with the client). Profiles or deployments of this specification should clearly document the conditions under which a client should expect a refresh token in response to urn:ietf:params:oauth:grant-type:token-exchange grant type requests.

@adeinega adeinega requested a review from dhs-aws as a code owner July 7, 2024 08:09
Copy link
Owner

@deansaxe deansaxe left a comment

Choose a reason for hiding this comment

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

lgtm

@deansaxe deansaxe merged commit cef9384 into main Jul 8, 2024
2 checks passed
@adeinega adeinega deleted the refresh_tokens branch July 8, 2024 16:06
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.

2 participants