Ignore throttling from clients #4
Open
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
jashan-lco
approved these changes
Aug 9, 2024
…d by the permission
mgdaily
approved these changes
Aug 12, 2024
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.
From: https://lco.sentry.io/issues/5692330034/?alert_rule_id=15340684&alert_timestamp=1723154286503&alert_type=email&environment=production¬ification_uuid=4e028941-860d-43b4-b2c2-78c459a7253c&project=4507652434165760&referrer=alert_email
It looks like the science archive has a default throttling scheme setup which is applying to the ocs-authentication's update user details endpoint. Since this endpoint already is authenticated with the special server token - I've set a throttling class to always allow it to pass throttling regardless of what the client app might have set as a default.