docs: make clear that any access token expiry dates are ignored #2644
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
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.
Description
Make clear in the documentation that oauth2-proxy will not consider expiry dates set within JWT access tokens.
Motivation and Context
People are occasionally confused that oauth2-proxy will not use an expiry date in JWT access tokens and do not realize they must set "cookie-refresh". The documentation was unclear on this issue. This PR fixes it and will hopefully pre-empt some issues. Briefly discussed in Slack.
How Has This Been Tested?
Hasn't been tested beyond the Github Markdown parser.
Checklist: