Internal API calls guards during OAuth 2.0 authentication #1691
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
duytiennguyen-okta
approved these changes
Sep 4, 2023
MikeMondragon-okta
force-pushed
the
internal_api_guard
branch
from
b76417d
to
b6eccee
Compare
|
Okta internal reference: https://oktainc.atlassian.net/browse/OKTA-644888 |
Merged
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.
Guards against making internal API calls when the SDK client is using OAuth 2.0 authentication have been put in place.
Resources
okta_profile_mappingokta_app_oauthNote that resource
okta_security_notification_emailsandokta_rate_limitingare OAuth 2.0 incompatible.