Skip to main content

Search

Welcome to our Support Center

Hub Access via Single Sign-On (SSO)

Overview

SSO Configuration Guide

SSO Troubleshooting

SSO Overview

What is Single Sign-On (SSO)?

Single Sign-On (SSO) is a user authentication process that allows individuals to access multiple applications or systems with a single set of login credentials. This means that once a Learner logs in with their username and password, they can access various services without needing to log in again for each one. SSO simplifies the login experience, enhances security, and improves efficiency by reducing the number of passwords learners must manage.

Why is SSO Important?

SSO allows organizations to provide Learners access, bypassing the need for Challenger to bulk upload or ask learners to self-register. Instead, the organization’s IT department sets up Learners by "forcing access," minimizing the steps needed to take. This process increases accountability, as Learners cannot bypass registration. SSO is essential for organizations as it streamlines authentication, reducing the need to remember multiple passwords, enhances security by centralizing authentication, and allows for stronger security policies. It also improves Learner experience by reducing login friction, boosting productivity and satisfaction.

How Does SSO Work?

SSO works by using a trusted identity provider (IdP) to authenticate Learners. When a Learner attempts to access an application, the service provider (SP) redirects them to the IdP, which verifies their credentials. In this case, the SP is Challenger. Once authenticated, the IdP sends an authentication token back to the SP, granting the Learner access to the application. This process is typically handled through secure protocols like Security Assertion Markup Language (SAML) or OAuth. 

Note: the IdP is something you must already have - Challenger cannot provide one.

How to configure Single-Sign-On 

Once the decision is made to proceed with the SSO integration, your Challenger Implementation team will send you the following information via email:

  1. Comprehensive Guide
    • We provide dedicated guides for Azure and OKTA, as well as general instructions that are applicable across various identity providers (IdPs).
  2. Unique Client ID
    • This ID is crucial for the Challenger system to identify and differentiate your company from others. It will form a unique part of your company's SSO link.
  3. Metadata XML File
    • This file contains essential metadata required for the SSO setup.
  4. Certificate
    • This is a data file necessary for completing your SSO configuration. This file contains essential metadata required for the SSO setup.

We will need some information from you in return. Please submit to implementation@challengerinc.com:

  1. Group IDs/Associations
    • These are the specific group identifiers or associations within your organization that need to be linked to the SSO.
  2. Federation Metadata XML
    • Please supply the XML file that contains your federation metadata.
  3. Certificate (Base64)
    • Provide the Base64 encoded certificate required for the SSO setup.
  4. Attributes/Claims
    • Please provide the values/object IDs for the attribute/claim setup.

Ensure all the required information is accurate and complete to facilitate a smooth SSO configuration process.