- Notifications
You must be signed in to change notification settings - Fork928
chore: add faking 429 responses from fake idp#12365
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Required to trigger error condition in fe
| typeWith429Argumentsstruct { | ||
| AllPathsbool | ||
| TokenPathbool | ||
| AuthorizePathbool | ||
| KeysPathbool | ||
| UserInfoPathbool | ||
| DeviceAuthbool | ||
| DeviceVerifybool | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
idea: just supply a number of RegExes to match the given paths? That way you can reuse it however you like. But this is probably fine though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Yea, that would work too. I think this is fine though. It's so niche. I just made it to reproduce this:#12367
Felt like I should just throw it in a PR. If someone wants to improve this later, they can. We could also replace the bool with a number and return 500s etc.
🤷
Uh oh!
There was an error while loading.Please reload this page.
Created this so I can reproduce a 429 issue in the FE:#11570 (comment)
Example run:
go run ./scripts/testidp/main.go --device-flow --429=device