Jump to: navigation, search

Single Sign-On

This feature requires specific configuration/updates on Genesys Management Framework components (LDAP, IdP, Config Server, and so on).

GMS version 8.5.003.xx and higher enables you to use Single Sign-on (SSO) to access the GMS Service Management UI. This page describes the settings needed to configure GMS to use your existing SSO infrastructure.


Initiates Security Assertion Markup Language (SAML) login procedure.


All authenticated Genesys users defined in Configuration Manager can access the GMS Service Management UI. GMS requires a valid user defined in Configuration Manager in order to allow administration tasks. Genesys Config Server must be configured to use external authentication functionality; Config Server users must be defined to use external authentication, pointing to the authentication system (LDAP, and so on).


Close the browser or remove browser cookies.


SSO deployment requires the following steps:


  1. Uncomment the SAML parameter in the launcher.xml file.
  2. Create keystore.
  3. Create server-settings.yaml file and configure the following settings:
    • adminUrl
    • caCertificate
    • jksPassword
    • encryptionKeyName
    • signingKeyName
    • identityProviderMetadata: idp-metadata.xml
  4. Start GMS.
    • Generate GMS metadata.
    • Update IdP information with GMS metadata.



Uncomment the following parameter in launcher.xml:

  <parameter name="saml-settings" displayName="saml-settings" mandatory="false">
    <description><![CDATA[GMS Server SAML init]]></description>
  	<format type="string" default="server-settings.yaml" />

Generating Security Keys

To generate a keystore, you can use the keytool utility that is included with Java SDK. To generate a JKS keystore, use the following command:

keytool -genkey -keystore keystore.jks -alias <encryptionKeyName>  -keypass <signingKeyName> -storepass <jksPassword> -dname <distinguished_name>


Security Keys

In order to enable SAML, you must specify the following mandatory properties in a general section into server-settings.yaml:

  • adminUrl (mandatory) - the URL will be used as unique entity ID in SP metadata.
  • caCertificate (mandatory) - a path to a key storage in JKS format containing all necessary keys.
  • jksPassword (mandatory) - a password for the key storage specified above.


adminUrl: http://<gmshost>:<gmsportport>/genesys/admin
caCertificate: c:\GMS\keystore.jks
jksPassword: password

SAML Settings Section

In order to enable SAML, you must specify the following mandatory properties in the samlSettings section into server-settings.yaml:

  • encryptionKeyName
  • signingKeyName
  • identityProviderMetadata


adminUrl: http://<gmshost>:<gmsportport>/genesys/admin
caCertificate: c:/GMS//keystore.jks
jksPassword: password
    encryptionKeyName: client
    signingKeyName: client
    identityProviderMetadata: idp-metadata.xml


Name Mandatory? Description
encryptionKeyName Yes SAML encryption key name. This key must be present in the JKS key storage specified above. This key is used to encrypt SAML message sent to IdP.
signingKeyName Yes SAML signing key name. This key must be present in the JKS key storage specified above.
responseSkewTime No Sets maximum difference between local time and time of the assertion creation, which still allows messages to be processed. Determines the maximum difference between clocks of the IdP and SP servers. Defaults to 60 seconds.

Note: You can use the same key for signing and encryption.

Identity Provider

Name Mandatory? Description
identityProviderMetadata Yes Identity Provider XML metadata file path or URL. If the IdP metadata file is exposed by the remote server over HTTP, it is possible to also specify the URL (default request timeout of 5 seconds will be applied). Check the metadata URL of your IdP server.

Generating GMS Metadata

GMS metadata (SP metadata) are available at the following URL:


Use this file to update your IdP server.

This page was last edited on November 24, 2017, at 09:50.
Comments or questions about this documentation? Contact us for support!