Configure SAML authentication

Security Assertion Markup Language (SAML) authentication allows you to use common external identity providers (IdP) to authenticate user names and passwords for Calabrio ONE (the service provider, or SP). This method of user authentication and password management is commonly referred to as single sign-on (SSO).

If you are using SAML and you want to let your agents access their schedules outside of work through a third-party calendar such as Microsoft Outlook, Google Calendar, or Apple Calendar, select the “iCal Sync with SSO” check box on the Global Settings page for WFM (see Configure system-wide WFM settings). For more information about how to configure Calabrio ONE so that agents can access their schedules outside of work when SAML is enabled, see View your schedule in another calendar app.

NOTE   Tenant administrators who have been added by a system administrator can always log in using their Calabrio ONE credentials. This is true even if Calabrio ONE authentication is disabled and another form of authentication (SAML or Active Directory) is enabled.

Configuring identity providers

Calabrio ONE integrates with all IdPs that support SAML 2.0 authentication. The following general parameters apply when configuring the SAML assertion in an IdP.

For more information about configuring specific IdPs, see Configuring Okta and Configuring ADFS

Assertion Component Configuration

Attributes

The IdP must send an assertion containing your users’ email address as an attribute. This email address must match the address used for Calabrio ONE authentication.

EXAMPLE   

The specific name of the email attribute depends on the IdP that you use. The following are examples:

  • EmailAddress
  • Email
  • Mail
  • User.email

Signatures

The SAML assertion must be signed. Assertions can be signed with the following algorithms:

  • RSA-SHA1
  • RSA-SHA256

Key sizes

Encrypted assertions are supported only with a maximum key size of 128 bits.

Calabrio ONE can integrate with both SP-initiated and IdP-initiated SAML, depending on the IdP that you use.

IdP Supports SP-Initiated SAML Supports IdP-Initiated SAML

Okta

Yes

Yes

ADFS

Yes

Yes

Azure

No

Yes

Other IdPs

Varies

Varies

NOTE   For IdP-Initiated SAML using Azure AD, the Sign on URL field in the app in Azure AD must be empty.

Field descriptions

The following fields appear when you select Enable SAML Authentication.

Managing service provider certificates for Calabrio ONE

Not all IdPs or IdP configurations require service provider certificates.

IdP Certificate Required

ADFS

Yes

Okta

No

Other IdPs

Varies by configuration.

If your IdP or IdP configuration requires a service provider certificate to integrate with Calabrio ONE, you have several options, depending on whether your Calabrio ONE deployment is in the cloud or on premises.

Deployment Option

Cloud, On Premises

Use the default global certificate provided by Calabrio ONE.

Cloud, On Premises

Import a self-managed certificate and private key.

The certificate can be self-signed or it can come from a third party (for example, Verisign or DigiCert). The syntax of the private key must be PKCS 8.

On Premises

On the server where you installed Calabrio ONE, save a self-managed certificate and private key in the shared configuration directory. This directory is the UNC path that was entered during Calabrio ONE installation. See the “Installing Calabrio ONE” section of the Calabrio ONE Installation Guide for On Premises Deployments.

The certificate and private key must have the following names:

  • Certificate—serviceProvider.crt
  • Private Key—serviceProvider.key

The certificate can be self-signed or it can come from a third party (for example, Verisign or DigiCert). The syntax of the private key must be PKCS 8.