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

Treat sts::IdpCommunicationError as a transient error #966

Closed
Tracked by #1583 ...
rcoh opened this issue Dec 13, 2021 · 1 comment · Fixed by #1718
Closed
Tracked by #1583 ...

Treat sts::IdpCommunicationError as a transient error #966

rcoh opened this issue Dec 13, 2021 · 1 comment · Fixed by #1718
Assignees
Milestone

Comments

@rcoh
Copy link
Collaborator

rcoh commented Dec 13, 2021

Currently, it's modeled as an unretryable client error. This needs to either be modeled upstream or as a customization

@rcoh rcoh added this to the GA milestone Dec 13, 2021
@Velfi Velfi mentioned this issue Jul 27, 2022
5 tasks
@jdisanti jdisanti mentioned this issue Aug 31, 2022
28 tasks
@jdisanti
Copy link
Collaborator

jdisanti commented Sep 7, 2022

The modeled error type for this: com.amazonaws.sts#IDPCommunicationErrorException

Documentation:

The request could not be fulfilled because the identity provider (IDP) that was asked to verify the incoming identity token could not be reached. This is often a transient error caused by network conditions. Retry the request a limited number of times so that you don't exceed the request rate. If the error persists, the identity provider might be down or not responding.

@jdisanti jdisanti self-assigned this Sep 7, 2022
@jdisanti jdisanti moved this to In Progress in AWS Rust SDK Public Roadmap Sep 7, 2022
@jdisanti jdisanti moved this from In Progress to In Review in AWS Rust SDK Public Roadmap Sep 8, 2022
Repository owner moved this from In Review to Done in AWS Rust SDK Public Roadmap Sep 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants