Setting Up OKTA/SAML on a Multi-Tenant Instance

Overview 

In order to provide the ability to sign into a Decisions in a Multi-Tenant environment using SSO (Single Sign On), users may set up the OKTA/SAML Module on the InstanceDefaultSetupPrototype. The following document demonstrates how to properly set up this Module properly for use in a Multi-Tenant environment.

Installation

To setup OKTA/SAML Module on a Multi-Tenant Instance: 

1. Login into the InstanceDefaultSetupPrototype with its associated administrative Account. 
2. From the Decisions Studio, navigate to System > Administration > Features. 
3. Locate SAML from the Available Features list, click INSTALL, and confirm the installation by clicking YES. 
4. After the Module installs, on the File System, navigate to C:\Program Files\Microsoft SQL Server\MSSQL[VERSIONNUMBER].MSSQLSERVER\MSSQLL\Backup and delete the InstanceDefaultSetupPrototype.bak file. 
   Additional Info on Backups

   If the user wishes to save current settings, the Backup file may be moved to a separate location and used as a restoration instead of deleted. 

   

   
   

5. Navigate back to the Decisions Studio on the Prototype Instance. Then, right-click the System Folder, select Restart Instance. then RESTART.

6. Navigate back to Hosting > Customers > ContractDefaultSetupPrototype on the Primary Instance. Right-click the Default Hosting Configuration and select Add Instance.

7. From the Add Instance screen, define the Instance, then click ADD INSTANCE.

   Additional Information on Add Instance 

   For more information on adding an Instance to a Multi-Tenant environment, see Adding an Instance in Multi-Tenancy

   

8. Right-click the newly added Instance and select Control Instance > Start.  
   
   
9. Once the Instance's status changes to Started, login to the Account affiliated with the Instance. Then, navigate to System > Administration > Features to verify that the Instance has the SAML Module preinstalled.