In Basic SAML Configuration, click Edit and type the appropriate Genesys Cloud SAML login URL in the Reply URL and Logout URL fields.Note: Select the one published by Genesys Labs Inc. You can either configure the Genesys Cloud gallery application (preferred method) or create a custom Genesys Cloud application. Single sign-on will not work using the desktop app in this configuration. If you have configured an Azure Conditional Access policy that requires a browser extension, you will need to use a Genesys Cloud supported browser that has the Azure AD extension installed. The Genesys Cloud desktop app does not support the installation of browser extensions.Clock skews between Genesys Cloud and your identity provider cannot be greater than 10 seconds. The problem might be caused by the length of the clock skew between the SP and the IdP. This problem can result in users getting locked out of their single sign-on when logging in. There is a general problem when a Service Provider (SP) receives a SAML response from an Identity Provider (IdP) and their system clocks are not in sync.

If one certificate becomes invalid or expires, the backup certificate will preserve the integration. Administrators can choose to store one additional certificate to ensure business continuity.For more information, see Configure Genesys Cloud to authenticate with SSO only. Administrators can optionally disable the default Genesys Cloud login and enforce authentication using an SSO provider only.Since the channel is encrypted, there is no need to encrypt parts of the message. The Genesys Cloud log in service requires Transport Layer Security (TLS). Genesys Cloud does not support assertion encryption for single sign-on third-party identity providers.

Azure active directory single sign on