Which feature requires at least one single sign-on (SSO) integration to be configured before allowing a user to login to Genesys Cloud CX?

Question breakdown

Tests

Single sign-on and authentication settings

Difficulty

Easy

Key idea: The 'Disable Genesys Cloud Login' setting forces users to authenticate through an identity provider, so at least one SSO integration must exist first.

How to reach the answer

1. The clue is a feature that needs SSO in place before users can log in.
2. Turning off native Genesys Cloud credentials leaves SSO as the only way to log in.
3. Without a configured SSO provider, nobody could authenticate, so the platform requires SSO first.
4. Password expiration and the other options do not depend on SSO.

Each option

• AIncorrect. Disable Location Detection is about presence and location prompts, not authentication method.
• BIncorrect. Password Expiration applies to native Genesys Cloud passwords and needs no SSO.
• CCorrect. Disabling Genesys Cloud login removes native credential login, so an SSO integration must be configured for users to sign in.
• DIncorrect. Open Admission is not an authentication feature tied to SSO configuration.

Common trap: Password Expiration sounds security-related and can seem linked to identity settings, but it only governs native passwords.

In practice: Organizations moving to Okta, Azure AD or ADFS usually configure and test SSO first. They then disable Genesys Cloud login to enforce IdP-only access and keep a recovery plan for admins.

Remember: Disable Genesys Cloud Login requires at least one working SSO integration, because it removes native credential login.

Drafted with AI assistance and checked against the answer key.