feat: add application provisioning (SCIM) tools - #72
Open
mjdavidson wants to merge 1 commit into
Open
Conversation
There was no way to configure outbound SCIM provisioning (directory sync) on an application, so an app could not be pointed at an external SCIM endpoint through the server. Add tools covering the connection and feature endpoints: - get_app_provisioning_connection / set_app_provisioning_connection (base URL + bearer token, TOKEN auth) / activate / deactivate - list_app_features / update_app_feature (configure create/update/deactivate user and group-push capabilities) The two request bodies are SDK oneOf unions, so they are built via from_dict to bind the concrete variant — otherwise the base URL, token, and capabilities would serialize to an empty body. Reads gate on okta.apps.read and writes on okta.apps.manage, with registry entries and README updates. On an app that does not support provisioning, Okta returns HTTP 200 with the connection status and auth scheme both set to UNKNOWN (no error). The connection tools detect that sentinel and return an explicit error instead of a response that looks half-configured.
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
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.
There was no way to configure outbound SCIM provisioning (directory sync) on an application. Adds connection tools (
get/set/activate/deactivate— base URL + bearer token, TOKEN auth) and feature tools (list_app_features/update_app_feature). The request bodies are SDK oneOf unions built viafrom_dictso the base URL, token, and capabilities actually serialize. On an app that does not support provisioning, Okta returns HTTP 200 withstatus/authScheme=UNKNOWNand no error; the connection tools detect that sentinel and return a clear error.Tests:
tests/test_app_provisioning.py.