Authentication, Login, and SSO Release Notes
Not all releases or changes listed below may pertain to your deployment. Check the table below to see which releases apply to you.
|Service||Released on||Released for||Highlights|
|Authentication Service||October 04, 2021||Updated versioning scheme|
|Authentication Service||September 09, 2021||Support for Red Hat OpenJDK 11 and authenticated database connections. Support for arbitrary UIDs in private edition deployments on OpenShift.|
|Authentication Service||April 19, 2021||Support for Identity Provider-initiated (IdP-initiated) login. Early Adopter Program support for Genesys Engage cloud private edition.|
|CCE Auth||March 31, 2021||Support for Genesys Engage cloud on Azure|
|Authentication API||March 31, 2021||Support for Genesys Engage cloud on Azure|
|Authentication Service||March 31, 2021||Support for Genesys Engage cloud on Azure|
Authentication Service: October 04, 2021
- Genesys Authentication now includes a build number as the last portion of the version string. (AUTH-1090)
Authentication Service: September 09, 2021
- Authentication Service now supports Red Hat OpenJDK 11. (AUTH-833)
- Authentication Service supports multiple Identity Provider (IdP) configurations within the same regional deployment for the tenant. This feature is available for select customers as part of the Early Adopter Program. Contact your Genesys representative for more information. (AUTH-765)
- Authentication Service supports authenticated connections to the PostgreSQL and Redis databases it uses. (AUTH-465)
For private edition
- Genesys Authentication now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
- The Dockerfile has been modified to specify container and file ownership as user=500 (genesys) and group=0 (root).
- The securityContext settings exposed in the default values_gauth.yaml file specify the user and group IDs for the genesys user (500:500:500). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs. For more information, see Configure Genesys Authentication.
- Genesys Authentication is deployed using ServiceAccounts that use the restricted Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom genesys-restricted SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the genesys-restricted SCC has been deprecated. If you previously deployed Genesys Authentication using the genesys-restricted SCC, Genesys recommends that you redeploy Genesys Authentication so that you use arbitrary UIDs. (AUTH-1011)
Authentication Service: April 19, 2021
- Authentication Service now supports Identity Provider-initiated (IdP-initiated) login using the SAML Single Sign-on integration. When a user is logged in to their external IdP, they can click a link and directly log in to a Genesys Engage application. (AUTH-469)
More info: IdP-initiated login
- The login page for Genesys Engage cloud applications now always displays the Tenant field. Users must enter a tenant if their username is not an email address or is an email address that is not associated with a single Genesys Engage cloud tenant. (AUTH-440)
More info: Log in to Genesys Engage cloud
- Authentication Service now accepts a configurable maximum age for a SAML assertion. The default remains 2 hours. Contact your Genesys representative to request a change to the maximum SAML assertion age configuration. (AUTH-424)
More info: SAML settings
- Authentication Service now supports enforceAuthN in SAML authentication requests. When enabled, Authentication Service sends an attribute to the IdP that tells it to re-authenticate the user, regardless of their previous state. Contact your Genesys representative to enable this feature. (AUTH-423)
More info: SAML settings
For private edition
- Starting with this release, Authentication Service is available for select customers in Genesys Engage cloud private edition, as part of the Early Adopter Program. (AUTH-724)
More info: Genesys Authentication Private Edition Guide
CCE Auth: March 31, 2021
- Starting with this release, CCE Auth is available in Genesys Engage cloud on Azure.
Authentication API: March 31, 2021
- Starting with this release, Authentication API is available in Genesys Engage cloud on Azure.
Authentication Service: March 31, 2021
- Starting with this release, Authentication Service is available in Genesys Engage cloud on Azure.
For information about prior releases of Authentication Service, click here: Authentication Service
For information about prior releases of Authentication API, click here: Authentication API