How to set up Okta SAML SSO with ClickView

Single Sign-On

Summary

  • Sign in to the Okta Admin Console using your organisation URL.
  • Create a new application integration using SAML 2.0.
  • Configure required SAML fields, including the Single Sign-On URL and Audience URI.
  • Add attribute statements for user information and access identification.
  • Assign groups to the ClickView application.
  • Copy the Metadata URL and submit it using the onboarding form.
star icon
Quick tip
In ClickView, how do I configure Okta for SAML single sign-on?
To configure Okta SAML SSO, administrators create a ClickView SAML 2.0 app in Okta, define the required SAML settings and attribute statements, assign user groups, and provide the Metadata URL through the onboarding form.

Okta SAML SSO integration overview

This article explains how to configure a SAML 2.0 application in Okta for use with ClickView and submit the required metadata so the SSO instance can be set up.

Configure a SAML 2.0 app in Okta

  1. Sign in to the Okta Admin Console using your admin account and your unique organisation URL, typically formatted as:
    • https://<subdomain>.okta.com
  2. Go to Applications and select Select Applications.
    Okta applications interface
  3. Select Create App Integration, then set Applications Sign-in method to SAML 2.0. Click Next.
    Create a new app integration pop up
  4. When prompted, enter the App name as ClickView, then continue by clicking Next.
    Create SAML integration interface

Configure SAML settings

  1. In the Configure SAML section, populate or select the following fields exactly as shown:
    • Single sign-on URL
      https://saml-in5.clickview.com.au/Shibboleth.sso/SAML2/POST
    • Audience URI (SP Entity ID)
      https://saml-in5.clickview.com.au/shibboleth
    • Name ID format
      EmailAddress
    • Application username
      Email
      Create SAML integration with filled information
  2. After completing these fields, continue using Next. The ClickView application will now appear in Applications. Return to Applications, then open ClickView.
    Okta applications interface

Add attribute statements

  1. Open the Sign On sub-tab for the ClickView application.
    Sign-on sub tab in applications
  2. Scroll to the Attribute statements section and select Add expression.
    Attribute statements section
  3. Add the following expressions:
    • Name: firstName
      • Expression: user.profile.firstName
    • Name: lastName
      • Expression: user.profile.lastName
    • Name: mail
      • Expression: user.profile.login
        Expressions added in attribute statements

Additional user attributes

Two additional user attributes are required to complete the SSO configuration:

  1. Access level attribute
    • This attribute is used to identify the user’s level of access within ClickView, such as a student grade level or staff role.
      Access level attribute
  2. School identification attribute
    • This attribute is used to identify the user’s school or site within a MAT. The attributes used depend on the customer’s Active Directory or Okta configuration.
      School identification attribute

Note:

  • The attributes used depend on the customer’s Active Directory or Okta configuration.
  • There are no fixed attribute names required.
  • Any existing attributes may be used, provided they accurately represent the user’s access level and school.

This is what a user’s profile and attribute values will look like:

User’s profile and attribute values interface

Assign groups to the ClickView application

  1. Navigate to Applications, open ClickView, then go to Assignments and select Groups.
    Assigning groups interface
  2. Search for the groups you want to enable access to ClickView and assign them to the application.
  3. Navigate to Applications ClickViewSign On -> Metadata URL. Copy the Okta Metadata URL.

Submit SSO information

Once you have the Metadata URL, complete the onboarding form so the SSO instance can be set up.

Frequently asked questions

No. There are no fixed attribute names required. Existing attributes may be used if they accurately represent the user’s access level and school.
These attributes allow ClickView to identify a user’s role and their school or site within a larger organisation, such as a multi-academy trust.

Get in touch

If you’re having trouble finding the right topics or videos, just reach out! Our team - Akhil photoDaniel photoJalaj photo Akhil, Daniel, Jalaj, or any of us at ClickView - will be happy to help you get sorted.

Give feedback

Was this guide helpful?

Up Next

How to set up ADFS SSO for MATs

This article provides step-by-step instructions for MAT administrators integrating ClickView with Microsoft ADFS using the SAML protocol. It covers certificate requirements, federation metadata setup, relying party trust configuration, claim rule creation, endpoint settings, and submitting onboarding information.