Objective
Utilizing Okta to log into Invoca via SSO/SAML
Applies To
SSO SAML setup for companies that utilize Okta as their IdP
Procedure
- In the Admin Console, go to Applications > Applications.
- Click Create App Integration.
- Select SAML 2.0 as the Sign-in method.
- Click Next.
- Provide the general information for the integration and then click Next. Here is an Invoca icon that you can add to your app:
- Provide the necessary SAML settings information for your integration. Please note that your configuration might differ from this screenshot as the drop-down options are unique to your application.
- If you encounter challenges while mapping the necessary parameters, such as phone numbers, it may be necessary to create a custom attribute and add this new attribute to the app. Please remember that the app should be fully created before you can proceed with mapping new custom attributes. For further guidance on how to create and map custom attributes in Okta, please refer to this article .
- Click Next.
- Provide configuration information about your app integration to Okta, then select Finish.
Part 2 - Enable SSO in Invoca
Follow the steps in our How to allow users in your Invoca network to log in via SAML Single Sign-On (SSO) help article. Please note that all the fields must be filled out before you can get the metadata.
If you are unsure how to locate your SHA-265 Fingerprint, this help article will walk you through the steps: https://community.invoca.com/t5/how-to/how-to-find-your-sha-1-or-sha-256-fingerprint-for-your-sso/...
Part 3 - Configure the SSO settings in Okta
Once the tile is configured there are instructions on how to complete the SAML setup in Okta - Click on the button titled View SAML setup instructions, this will provide you with the necessary steps to enter Invoca's SAML endpoint(s), and metadata.
Part 4 - Test the Okta tile and Optional Cleanup
Testing best practices:
Once the SSO settings in Invoca have been completed and your Okta tile has SAML all setup, navigate to the Okta User Home page and test the tile. It's encouraged to create a Group in Okta and/or Group Rules for testing before inviting all users to the new SAML Invoca app. If you were able to sign Invoca successfully from Okta then you've completed this task. Congrats!
Optional Cleanup:
When enabling SSO for users, it's important to be aware that there will be two different authentication types for the same user.
If you decide to make SSO SAML requirements "mandatory for all users," we strongly recommend removing the 'Credentials' User to avoid locking out this account. Before removing the 'Credentials' User, be sure to add any saved Reports to the 'Single Sign On' User as these reports will not be transferred over automatically.
Help articles if you encounter a 403 error code:
Additional Information
A certified Okta Admin is required for this configuration.