Manage Login Authenticators

Login authenticators control how users log in to CXone. CXone supports both internal and external authentication based on the login authenticator that is assigned to the user and the type and configuration of that login authenticator.

For more information about authentication and authorization in CXone, click here.

Configure a System Login Authenticator

Required permissions: Can manage passwords, On.

CXone includes a default system login authenticator but you can create your own as well. After you configure a login authenticator for a particular role, the password field displays the configured login authenticator rules when a user tries to set or change the password.

1. Click the app selector and select Admin.
2. Go to Login Authenticator.

3. Click Create New.

4. Enter a unique Name for the login authenticator.

5. Enter a Description if you want one.

6. Select System as the Authentication Type.

   Learn more about authentication types

   Field	Details
   System	The login authenticator uses the built-in login process of CXone. It doesn't authenticate using an external single sign-on (SSO) identity provider.
   SAML	SAML 2.0 allows you to set up single sign-on through an external identity provider. CXone supports multiple instances of SAML 2.0. You can assign different instances to different users.

7. Set up your password complexity.

   Each user's password is checked against a repository of commonly used passwords. If their password matches one of the commonly used passwords, they will be forced to create a new password. Some of the passwords that are rejected include:

   • Any password that includes the word "password." For example, Password@1234.

   • Any password that includes the user's email address, username, first name, last name, or system name.

   Passwords are checked against this repository whenever:

   • A new user is activated.

   • A user's password expires.

   • A user resets their password.

   Learn more about fields in this step

   Field	Details
   Require Lower Case (a-z)	Requires users to use at least one lower-case letter in their passwords.
   Require Upper Case (A-Z)	Requires users to use at least one upper-case letter in their passwords.
   Require Numeric (0-9)	Requires users to use at least one number in their passwords.
   Require Non-alphanumeric (!,@,#,etc.)	Requires users to use at least one non-alphanumeric character in their passwords.

8. If you want to enable multi-factor authentication, select Require Multi-Factor Authentication. Set your MFA Type as HOTP and TOTP.

   Learn more about the MFA settings

   Field	Details
   Require Multi-factor Authentication	Requires users to enter a multi-factor authentication (MFA) token in addition to their password to log in to CXone. An MFA token is a one-time password generated by a hardware token or virtual MFA device (for example, an app like Google Authenticator) that you provide. When you enable MFA, users with the affected profile must configure an MFA secret key the next time they log in. You should not enable MFA for the master administrator in your organization. If the device or secret is lost, the only way to reset the MFA secret is to file a ticket with NICE CXone.
   MFA Type	Specifies whether you want to enable TOTP or HOTP MFA.

9. Set your password policy.

   Learn more about fields in this step

   Field	Details
   Password Length	Enter the minimum number of total characters users must include in their passwords. For example, if you enter12, users must include at least 12 total characters in every password. The characters required in the Password Complexity settings count towards the total character count. You can set the password length to any number between 12 and 24.
   Enable Password Age	Enables a text box where you can enter the maximum number of days a user can keep a password. After the specified number of days, the user must change their password. You can set the password age anywhere from 14 to 365 days.
   Enable Password History	Enter the number of unique passwords a user must set before they can reuse an old one. You can set the password history anywhere from 4 to 50. For example, if you enter 10, users assigned to the login authenticator cannot use any of their last 10 passwords as their new password.

10. Click Create Login Authenticator.

Set Up an External Login Authenticator with SAML 2.0

You can use external authentication when you want a user's password to be managed by another system or identity provider. CXone currently supports SAML 2.0 and OpenID Connect federation protocols.

You can set up IdP-initiated authentication or SP-initiated authentication with the steps in this section.

IdP-Initiated Authentication: IdP stands for identity provider. IdP-initiated authentication means that the external identity provider starts the login process.

SP-Initiated Authentication: SP stands for service provider. SP-initiated authentication means that CXone starts the login process.

1. Ensure that you have access to the external identity provider. You will need to create an integration specific to CXone.
2. Create the integration in the external identity provider. Different systems use different names for these integrations, see specific instructions for Okta or Azure.
   1. You will need to provide an Entity ID which you don't know at this point. Use https://cxone.niceincontact.com/need_to_change as a placeholder.
   2. You will need to provide an ACS URL which you don't know at this point. Use https://cxone.niceincontact.com/need_to_change as a placeholder.
   3. The identity provider will generate a specific URL where SAML requests must be sent. Copy and save this URL to a place where you can find it. You will need to enter this value in later steps.
   4. The identity provider will generate a public signing certificate for the integration. Download the certificate. You will need to use it in later steps.
3. Create an external login authenticator in CXone.
   1. Click the app selector and select Admin.
   2. Click Security > Login Authenticator.
   3. Enter the Name and Description of the login authenticator.
   4. Select SAML as the Authentication Type.
   5. If you select FICAM, the SAML response must have a single AuthnContextClassRef entry. Also, the NamespaceURI of the assertion subject must be: urn:oasis:names:tc:SAML:2.0:assertion. The AuthnContextClassRef and NamespaceURI fields are controlled by the identity provider.
   6. Enter the SAML request Endpoint you received from your provider above as the Endpoint URL.
   7. Click Choose File and select the public signing certificate you received from your provider. This file must be a PEM file. It will be a text file and the first line will contain BEGIN CERTIFICATE with some other text.
   8. Click Save and Activate.
   9. Open the login authenticator.

   10. Note the Entity ID and ACS URL. You will need them when updating your IdP settings.

4. Update your identity provider settings, replacing the placeholders used above with the values you just noted.

5. Ensure that the External Identity for each user that uses the login authenticator is set to the correct value.

   Your identity provider determines the value that must be used. The value must match exactly what you put in the External Identity field in CXone.

6. Have the user log in. They must use the latest login URL. After entering their username they will be directed to the external identity provider if needed.

Create External Login Authenticators with OpenID Connect

Required permissions: Login Authenticator Create

You can use external authentication when you want a user's password to be managed by another system or identity provider. CXone currently supports SAML 2.0 and OpenID Connect federation protocols.

You can set up SP-initiated authentication with the steps in this section.

SP-Initiated Authentication: SP stands for service provider. SP-initiated authentication means that CXone starts the login process.

1. Ensure that you have access to the external identity provider. You will need to create an integration specific to CXone.
2. Create the integration in the external identity provider.
   1. You will need to provide a Sign-in Redirect URI which you don't know at this point. Use https://cxone.niceincontact.com/need_to_change as a placeholder.
   2. You may need to provide a Sign-out Redirect URI which you don't know at this point. Use https://cxone.niceincontact.com/need_to_change as a placeholder.
   3. The identity provider will generate a Client ID and a Client Secret. Copy and save these values where you can find them. You will need to enter them in later steps.
3. Create an external login authenticator in CXone.

   1. Click the app selector and select Admin.

   2. Click Login Authenticator.

   3. Click Create New or select the login authenticator you want to edit.
   4. Enter the Name and a Description of the login authenticator.
   5. Select OIDC as the Authentication Type.
   6. If you have a discovery endpoint for your IdP, click Discover Settings. Enter your discovery endpoint and click Discover. The remaining fields are populated for you. Discover Settings does not work with Salesforce discovery endpoints.
   7. Enter your Client Identifier and Client Password. Re-type the password in Client Confirm Password. The Client Identifier is the login ID assigned to your account by your IdP.

   8. If you don't have a discovery endpoint for your IdP, enter your IdP-provided Issuer, JsonWebKeySet Endpoint, Authorization Endpoint, Token Endpoint, UserInfo Endpoint, Revocation Endpoint, and End Session Endpoint.

      Learn more about fields in this step

      Field	Details
      Issuer	The URL of your IdP without any parameter.
      JsonWebKeySet Endpoint	The URL of your IdP's JWK Set.
      Authorization Endpoint	The URL of your IdP's OAuth 2.0 Authorization Endpoint.
      Token Endpoint	The URL of your IdP's OAuth 2.0 Token Endpoint.
      UserInfo Endpoint	The URL of your IdP's UserInfo Endpoint.
      Revocation Endpoint	The URL of your IdP's Revocation Endpoint.
      End Session Endpoint	The URL of your IdP's End Session Endpoint. This field allows you to create a single logout experience for your users. If configured, when they log out of CXone, they will also be logged out of their IdP account. For single logout to work, you must whitelist the Sign-out Redirect URI in your IdP.

   9. Select a Client Authentication Method. The method you select must be an authentication method that your IdP supports. If you select private_key_jwt, you must select Enable Encryption and enter your Client Assertion Verification Key.
   10. You can select Enable FICAM Profile to turn on U.S. government-specific settings.
   11. Click Create Login Authenticator to validate the provided information and to link your CXone account to your IdP account.
   12. Open the login authenticator.

   13. Note the Sign-in Redirect URI and Sign-out Redirect URI. You will need them when updating your IdP settings.

4. Update your identity provider settings, replacing the placeholders used above with the values you just noted.

5. Ensure that the External Identity for each user that uses the login authenticator is set to the correct value.

   Your identity provider determines the value that must be used. The value must match exactly what you put in the External Identity field in CXone. The value for this field must be in this format: claim(email):{email configured by your IdP}. For example, if the user's email in the IdP is nick.carraway@classics.com, you would enter claim(email):nickcarraway@classics.com.

6. Have the user log in. They must use the latest login URL. After entering their username they will be directed to the external identity provider, if needed.

7. When your IdP asks you to authenticate, do so as the user on the IdP you want associated with your currently logged in CXone account.
8. If your OpenID Connect settings in CXone don't show as validated, use your IdP logs to diagnose the problem.

Linking New Users with Claim-based OpenID Connect

CXone can use a different claim value, like an email address, to establish the user's identity at their first login. CXone then automatically switches to the unique OpenID Connect subject identifier. This allows you to pre-configure a user's federated identity.

PKCE for Front-End Authentication

You may have difficulty using the OpenID Connect authorization code flow. This flow requires a client_secret as part of the token exchange. Coding the client_secret into a web application is a security risk. OpenID Connect allows an alternative flow called PKCE (Proof Key for Code Exchange). PKCE uses a different authentication method. NICE CXone supports PKCE flows for front-end integrations.

Assign Users to the Login Authenticator

1. Click the app selector and select Admin.

2. Click Users.

3. Select the user that you want to assign to the login authenticator, or click Create New to create a new user.

4. On the General tab, click Edit.

5. In the Security section, select the login authenticator you made previously from the Login Authenticator drop-down.

6. Click Done.