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
Allow configurable Okta service synchronization duration. #31170
Conversation
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.
Just so I understand this right - suppose there are 1000 entities in Okta that get synced.
Wouldn't this change result in the following behavior:
- write 1000 things to the backend in a short period of time
- wait for some amount of time
- repeat
If that's the case, won't we still experience throttling? Should we instead insert a delay in between each of the 1000 writes?
This is for the Okta API throttling rather than the backend throttling. The backend is being throttled within the Okta service, limiting to roughly 5 writes per second FWIW. |
The time between Okta service synchronizations is now configurable. This will assist in slowing down Okta rate limits for users who have a significant number of Okta applications. The duration has been added to auth preference to allow users to tune this value when using the Okta plugin.
af95906
to
747471c
Compare
The time between Okta service synchronizations is now configurable. This will assist in slowing down Okta rate limits for users who have a significant number of Okta applications. The duration has been added to auth preference to allow users to tune this value when using the Okta plugin.