[6.8] Use refresh token for any access token error with 401 status code and re-authentication user for any refresh token error with 400 status code. (#33777) #60233
Conversation
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
… re-authentication user for any refresh token error with 400 status code. (elastic#33777) * Use refresh token for any access token error with 401 status code and re-initiate SAML handshake for any refresh token error with 400 status code. * Switch from `expect.js` to `@kbn/expect`. * Review#1: repurpose redundant tests to test token failures with 500 code.
Contributor
💚 Build SucceededTo update your PR or re-run it, just comment with: |
legrego
approved these changes
Mar 16, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Backports the following commits to 6.8: