Yes, SightCall supports Single Sign On using both SAML and OpenID Connect (OIDC)!
SAML
You may configure SAML SSO for agents and Admins (Admin Portal > Authentication):
"Add Configuration" then fill out the configuration page with your SAML provider's information. Here is a good example on how to configure Azure as SAML provider for agents
OpenID Connect
Creating an OpenID Configuration
To add a new OpenID authentication configuration:
Navigate to Administration → Authentication
Locate the OpenID Connect section
Click Add configuration
-
Select the target scope:
Agents
Admins
fill in the configuration according to your IdP's requirements:
Redirect URLs
These URLs must be configured in the Identity Provider.
Parameter |
Required |
Description |
|---|---|---|
Initiate Login URI |
Yes |
Endpoint used to initiate the OpenID authentication flow |
Sign-in Redirect URI |
Yes |
Callback URL used after successful authentication |
Example format:
Initiate Login URI
https://api-ppr.sightcall.com/auth/oidc/<DEFINED_ONCE_SAVED>/agent/start
Sign-in Redirect URI
https://api-ppr.sightcall.com/auth/oidc/<DEFINED_ONCE_SAVED>/agent/callback
<DEFINED_ONCE_SAVED>corresponds to the unique identifier generated once the configuration is saved.
General Parameters
Parameter |
Required |
Description |
|---|---|---|
Name |
Yes |
Name of the authentication configuration |
Default |
Optional |
Defines this configuration as the default authentication method |
Client ID |
Yes |
Client identifier provided by the Identity Provider |
Client Secret |
Yes |
Client secret associated with the Client ID |
Issuer URL |
Yes |
Base URL of the OpenID Identity Provider |
Auto-Provisioning
When Auto-Provisioning is enabled, the platform creates or updates the user based on the claim attributes returned by the SAML or OpenID Provider in the ID token and/or the UserInfo response. **If the user already exists, these fields do not get updated.
Three mappings must be configured to identify and populate the user account:
Login Mapping
(optional) The name of the IDP (SAML/OIDC) attribute that defines the user’s unique login identifier as the SightCall user ID.
This value should be:
stable over time
unique for each user
consistently returned by the Identity Provider
Typical value: preferred_username
Display Name Mapping
(optional) The name of the IDP (SAML/OIDC) attribute that defines the user’s displayed full name
Typical value: name
Email Mapping
(optional) The name of the IDP (SAML/OIDC) attribute that defines the user’s email address.
Typical value: email
The mapped value should be a valid email address and should be unique per user whenever email uniqueness is expected.
Usecase list mapping
(Optional) This is the name of the claim attribute, which contain a list of the usecase IDs of the Usecases to be assigned to the auto provisioned user. The example of the claim attribute value would be: [172, 246, 351]. Alternatively, you can use agent groups for easier management: in the Admin Portal, define a default agent group with associated use cases and call routings. Then, every new user automatically inherits these settings.