Installing and Configuring the Okta Module

Last Updated: 09/04/2018 Introduced in Version:

Installing the Okta Module

Warning: This will require appropriate technical resources on the clients side to be able to implement. We recommend making sure you have someone from your organization with experience available to streamline the process.  Our support team is available to help, but may not be not be able to answer questions or solve problems that are unique to your company.

Note: Accounts created before the following module is installed will need to be updated before using single sign on. Please contact support on how to update the account. 

 

To integrate Decisions with Okta, first install the Okta module. Installing modules may require administrator permissions in Decisions. In the Decisions Portal, navigate to System > Administration > Features. Locate the module Decisions.Okta and click Install.

For more information about installing a module in Decisions, see Installing a Module in Decisions.

Click YES to begin install.

You will see a notification that Decisions.Okta was successfully installed.

Before continuing, Decisions Service Host Manager must be restarted. Ensure all your current projects are saved and restart the service.

 

Configuring the Okta Module

 
To configure Okta, navigate to System > Settings then click Okta Settings.
 
 
From here you can manage Okta accounts & groups.
 

Configuring Subdomain or URL

 
You can configure the Subdomain or URL to be something like (https://dev-644101.oktapreview.com) or (https://<companyname>.okta.com)
 
The API Token can be retrieved (with an Okta admin account, in Okta) by going to Security > API > Tokens > Create Token
The Okta module uses the SAML module therefore changing the Okta settings actually passes the values through to the SAML settings.
 
Okta is a single specific provider whereas SAML is the protocol which is used by hundreds of different providers.

Additional Resources