Skip to main content

Setting Up SSO | Azure AD SAML

Written by Rochelle Sanderson
Updated this week

Overview

SSO configuration at Cotiss supports both Okta and Microsoft as identity providers (IDPs).

As part of onboarding with Cotiss and under your enterprise plan, this article focuses on integrating Azure Active Directory (Azure AD) for Single Sign-On (SSO) using SAML 2.0.

Our SSO uses JIT provisioning during the authentication flow to provision new users into Cotiss.

Who is this for?

The functionality of SSO is for Cotiss Buyers who require IT approval for their stakeholders to gain access to the Cotiss platform and are looking to simplify and automate this process.

This article is targeting a technical audience (your IT team) who would be the approver and team provisioning users in your organisation to Cotiss' SSO integration.

The implementation of SSO requires collaboration with your IT team and Cotiss. Please share the correct contact details with your Account Manager for them to facilitate this.

Responsibilities of Cotiss and your company (Client)

Client:

  • Set up and configure the Azure AD SAML 2.0 application in your Azure AD account.

  • Provide the XML Metadata URL and Certificate to Cotiss.

  • Provide timing on when to enable SSO for your account.

  • Provide and confirm the default Cotiss role for new users.

  • Responsible for assigning users and managing the user groups in Azure AD

Cotiss:

  • Provide Single sign-on URL & Audience URL to setup the integration.

  • Facilitate SSO and execute enablement at time/date specified by Client.

When SSO is enabled:

  • Users are matched based on email addresses

  • New users are provisioned through JIT (Just-In-Time) provisioning

  • The Evaluator user role is assigned to new users by default (see more on user roles here)

  • OTP (One-Time Password) authentication is automatically disabled

Important considerations:

  • The "Add user" and "Delete user" buttons in the Cotiss App are disabled when SSO is enabled so Cotiss Admins must ask their internal IT team to add access for new users

  • After SSO is set up the team member must login and activate their user profile via the Azure AD portal before they can gain access to the Cotiss account and be assigned to any events in Cotiss.

Implementing SSO with Cotiss

Before you begin

• Ensure you have admin access to the Cotiss App.

• Confirm your desired SSO go live date and timing for your account with your Account Manager

Steps to Implement:

  1. Azure AD Configuration

    • Log into the Azure Portal as an administrator.

    • Navigate to Azure Active Directory → Enterprise applications.

    • Select + New application → + Create your own application.

    • Provide a name (e.g., “Cotiss SSO”) and choose “Integrate any other application you don’t find in the gallery”.

  2. Configure SAML Single Sign-On:

    • Within the new application, select Single sign-on → SAML.

    • Configure using details provided by Cotiss:

    • Identifier (Entity ID): (Cotiss provided Audience URI)

    • Reply URL (Assertion Consumer Service URL): (Cotiss provided Single sign-on URL)

    • Set User Attributes & Claims:

    • Name Identifier: Email (user.mail)

    • Additional Attributes:

      1. FirstName: user.givenname

      2. LastName: user.surname

  3. After you have created the application, provide Metadata and Certificate to Cotiss:

    • Download and send Cotiss the following from Azure AD:

      • App Federation Metadata Url

      • Login URL

      • Signing Certificate (Base64 format)

Did this answer your question?