Okta Single Sign-On

This topic provides step-by-step instructions on how to set up SAML 2.0 with Okta. These settings will be used for both Web Server and Excel Add-in. As Okta, does not allow multiple ACS Url in the same application. We will need to create two different applications for Web Server and Excel Add-in.

Web Server

  1. Create a developer account on the Okta website at https://developer.okta.com/signup/.

  2. Click Applications on the menu.

  3. Click Create App Integration.

  4. Select SAML 2.0.

  5. In the App name field, enter SAML 2 Web Server.

  6. Click Next.

  7. In the Single Sign on URL field, copy the URL from the Saml2 ACS URL (Web Server) parameter in the Web Server.

  8. In the Audience URI (SP Entity ID) field, copy the URL from the Entity ID parameter in the Web Server.

  9. Click Next.

  10. Click Finish.

  11. Select the Assignments tab.

  12. Click Assign.

  13. Add the Nectari users who will be connecting with SSO.

  14. Download the Okta Certificate.

  15. Click the Sign On tab and select View Setup Instructions.

  16. Take note of the Single Sign-On URL and Identity Provider Issuer (Entity ID).

Excel Add-in

  1. Create a developer account on the Okta website at https://developer.okta.com/signup/.

  2. Click Applications on the menu.

  3. Click Create App Integration.

  4. Select SAML 2.0.

  5. In the App name field, enter SAML 2 Excel Addin.

  6. Click Next.

  7. In the Single Sign on URL field, copy the URL from the Saml2 ACS URL (Excel Addin) parameter in the Web Server.

  8. In the Audience URI (SP Entity ID) field, copy the URL from the Entity ID parameter in the Web Server.

  9. Click Next.

  10. Click Finish.

  11. Select the Assignments tab.

  12. Click Assign.

  13. Add the Nectari users who will be connecting with SSO.

  14. Download the Okta Certificate.

  15. Click the Sign On tab and select View Setup Instructions.

  16. Take note of the Single Sign-On URL and Identity Provider Issuer (Entity ID).

Frequently Asked Questions

This error shows up when the data received from OKTA to the Web Server/Excel Add-in doesn’t contain the user identifier that was configured within the Authentication screen. To resolve this issue, we will need to manually set the claims under the Attribute Statement section in OKTA.