Skip to content

feat: add OIN catalog browse and app-install tools#75

Open
mjdavidson wants to merge 1 commit into
okta:mainfrom
mjdavidson:feat/oin-catalog-app-tools
Open

feat: add OIN catalog browse and app-install tools#75
mjdavidson wants to merge 1 commit into
okta:mainfrom
mjdavidson:feat/oin-catalog-app-tools

Conversation

@mjdavidson

Copy link
Copy Markdown

Outbound SCIM provisioning only works on an instance of an OIN catalog app — provisioning capability is fixed by the catalog definition at install time and cannot be added to a plain custom app. create_application cannot install one because the typed SDK serialization strips the catalog name key. Adds list_catalog_apps/get_catalog_app to browse the OIN catalog and install_oin_app to install an instance via a direct POST that preserves name. Catalog reads gate on okta.apps.read, install on okta.apps.manage.

Tests: tests/test_oin_catalog.py.

Outbound SCIM provisioning only works on a provisioning-capable app, which must
be an instance of an OIN catalog app — provisioning capability is fixed by the
catalog definition at install time and cannot be added to a plain custom
SAML/OIDC app. create_application could not install one because the typed SDK
serialization strips the catalog 'name' key from the request body.

Add list_catalog_apps / get_catalog_app to browse the OIN catalog (find an app's
'name' and provisioning features) and install_oin_app to install an instance via
a direct POST that preserves 'name'. With an installed provisioning-capable app,
the existing provisioning tools (set_app_provisioning_connection,
update_app_feature, etc.) then work against it. Catalog reads gate on
okta.apps.read, install on okta.apps.manage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant