Explain how to deal with Rate Limiting in the OIDC providers doc #36362
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
gastaldi
approved these changes
Oct 9, 2023
gastaldi
approved these changes
Oct 9, 2023
|
Thanks @gastaldi for improving the text, laptop is in the office so I'll squash tomorrow, cheers |
sberyozkin
force-pushed
the
oidc_providers_rate_limiting
branch
from
ad2580b to
01a847a
Compare
|
I tried to cancel the doc workflow for now |
sberyozkin
force-pushed
the
oidc_providers_rate_limiting
branch
from
01a847a to
9f95033
Compare
|
Strange failure in the doc component: |
sberyozkin
force-pushed
the
oidc_providers_rate_limiting
branch
from
9f95033 to
ea8b5f6
Compare
|
🙈 The PR is closed and the preview is expired. |
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.
Many social OAuth2 providers which Quarkus will keep requesting to fetch UserInfo can be very restrictive so caching UserInfo is a way to manage such rate limiting policies.
PR also fixes another Mastodon text typo (George, I was too petrified to open a dedicated PR to fix it after spotting it shortly after fixing the image name typo :-) )