Use the Okta user access management connector
This article describes how to set up new provisioning workflows for OIN apps.
____________
Once you have completed setting up the Okta user access management connector, you must create new provisioning workflows for each OIN app, so that you can remove access to those apps via SSO if required. Once that’s done, de-provisioning works for OIN apps exactly the same way it works for all other apps at your installation that have Productiv connectors.
Note: The Okta Lifecycle Management and Okta Advanced Lifecycle Management SKUs are required for Okta de-provisioning. If you are unsure whether your instance of Okta Enterprise includes those SKUs, consult your system administrator.
Before you begin
Before you get started, look at the workflows that have already been set up.
To do this:
- Go to the Settings page.
- Open the “Access management” tab.
- Scroll down until you see the “App workflows” section.
- Click the “Apps with workflows setup” tab.
Provisioning workflow setup
For every app that you’d like to have de-provisioned via Okta SSO, do the following:
- To navigate to the app page, click the app name.
- Click the app page’s “Automation” tab.
- Look under Provisioning workflow to see if any workflow rules already exist.
- If a workflow already exists, edit it so that it uses the action method Remove SSO Access via Okta.
- If no workflow is yet set up, click an instance to create a new one.
-
- Click the “Deprovision” button to start setting up a deprovisioning workflow. Make sure to specify the action method as “Act via Okta” in the “Set access and provisioning outcome” step.
Read more
- For detailed information about how to manage app licenses with provisioning workflows, see Create provisioning workflows.
- For further information about the handoff between Productiv and Okta during deprovisioning, see About the Okta user access management connector.