Skip to main content
Skip table of contents

Technical Guide for SSO with Okta

"What is Single Sign On?"

Single Sign-On (SSO) is an authentication process that allows a user to access multiple applications or services with a single set of login credentials (such as username/email address and password). The primary goal of SSO is to simplify the user experience by eliminating the need to remember and enter different credentials for each application.

Single Sign-On (SSO) can improve security in several ways, but the two key advantages include:

  1. Reduced Password Fatigue - users only need to remember one set of strong credentials, reducing the likelihood of users choosing weak passwords or reusing passwords across multiple applications

  2. Consistent Security Policies - organisations can enforce consistent security policies across multiple applications. This ensures that security measures, such as password complexity requirements or account lockout policies, are applied uniformly.

https://developer.okta.com/docs/guides/oin-sso-overview/


Requirements


Stages

You will need to do the following to set up SSO with Okta.

  1. Obtain your Integration ID (See Configure Single Sign On (SSO) )

  2. Create App Integration

  3. Configure SAML Settings

  4. Finalising Your Application

  5. Provide your Metadata URL or Metadata XML (See Configure Single Sign On (SSO) )


Create App Integration

  1. Sign onto Okta

  2. Click Admin in the navbar

    1. You may be prompted to authenticate with your password or 2FA.

  3. In the sidebar click Applications > Applications

  4. Click Create App Integration

  5. Select SAML 2.0

You should now be able to fill in the General settings

Screenshot 2025-05-29 at 15.43.56.png
  1. Enter Axscend as the App Name

  2. Optionally, add Axscend Logo

  3. Click Next


Configure SAML Settings

You will need your Portal Integration ID.
You have Created App Integration.
You have completed Page 1 - General Settings.

Screenshot 2025-05-29 at 15.43.30.png

You will then need to configure the Basic SAML Details.

  1. Add the following details to SAML Settings:

  • Single sign-on URL: https://portal.axscend.com/auth/callback?company_id=XX

    • Replace company_id=XX with your unique company_id

    • Untick ‘Use this for Recipient URL and Destination URL’

  • Recipient URL: https://portal.axscend.com/auth/signon/sso/<Integration ID>

  • Destination URL: https://portal.axscend.com/auth/signon/sso/<Integration ID>

    • This will be the same URL as the Recipient URL.

  • Audience URI (SP Entity ID): https://portal.axscend.com/

  • Name ID format: EmailAddress

  • Application Username: Email

Screenshot 2025-05-29 at 14.54.45.png

  1. Continue to Attribute Statements

  2. Add the following:

  • Name: urn:oid:0.9.2342.19200300.100.1.3

    • This is the URI Reference for email address

  • Name Format: URI Reference

  • Value: user.email

Screenshot 2025-05-29 at 15.51.37.png

  1. Continue to Section B

  2. Click Next

Screenshot 2025-05-29 at 14.58.31.png

Feedback

Screenshot 2025-05-29 at 15.43.07.png

You will then be on the Page 3 - Feedback.

  1. Ensure you have selected Contact app vendor

    1. This informs Okta that the app you’re interacting with is external, and not part of your organisation.

  2. Click Finish

Screenshot 2025-05-29 at 15.00.44.png


Finalising Your Application

Immediately after saving, you should be redirected to the Sign On tab of the application you have created. This will show the Metadata URL.

Screenshot 2025-05-29 at 15.06.26.png
Can I upload an XML File?

For enhanced security, we recommend integrating using the Metadata URL. If you prefer, you can upload an XML file by saving the content from your Metadata URL into an XML file.

Now the application is set, you need to ensure users or groups are able to authenticate through this application.

  1. Click the Assignments Tab to configure which users should be included.

Screenshot 2025-05-29 at 15.06.48.png

You can now use your Metadata URL to Configure Single Sign On (SSO) on the Portal.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.