Add non-recoverable STS error codes - #7241
Open
alextwoods wants to merge 1 commit into
Open
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
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.
NOTE - Merges to feature branch and NOT master
Add non-recoverable STS error codes
Motivation and Context
Similiar to handling in SSO and Login providers, we want to not apply refresh backoff behavior (refresh resilliance) for errors that require customer intervention and would never recover.
Modifications
Adds a new STS non-recoverable predicate that checks all required error codes. This is done at the base class level rather than per specific STS subclass.
Testing
new unit tests + manual scenario.
Screenshots (if appropriate)
Types of changes
aster/docs/LaunchChangelog.md)
License