[v17] Okta: Fix creating Access Requests for legacy okta_service resources#54876
Merged
kopiczko merged 1 commit intobranch/v17from May 19, 2025
Merged
Conversation
kopiczko
changed the title
marcoandredinis
approved these changes
May 16, 2025
smallinsky
approved these changes
May 19, 2025
kopiczko
deleted the
kopiczko/okta__fix_legacy_okta_service_access_request
branch
Merged
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
With #53697 no plugin in the backend is interpreted as read-only integration (i.e. bidirectional sync disabled). In read-only mode we:
This PR changes that so missing plugin is NOT interpreted as read-only. This allows creating Access Requests for Okta-originated resources in the legacy setup with okta_service.
changelog: Okta: Fix creating Access Requests for Okta-originated resources in the legacy okta_service setup.