Handling 401 errors / okta_idp_saml #1369
Merged
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
need to be addressed.
When Orgs don't have Mappings API flag set, reading `okta_idp_saml` fails due to unauthorized access to mappings API.
MikeMondragon-okta
force-pushed
the
handle_401_403
branch
from
829214f
to
4a66add
Compare
duytiennguyen-okta
approved these changes
Nov 16, 2022
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.
Enhancing Fix okta_idp_saml resource reading when Mappings API is disabled #1355
okta_idp_samlresource reading when Mappings API is disabled #1355 fix