Jumunn

What's New

• The robustness of token-based authentication of requests from Genesys Administrator Extension (GAX) can be improved by using one or both of the following new configuration objects. Both options are set in the [system] section of Configuration Server or Configuration Server Proxy. The new options are:

  token-tolerance

  Default value: 60 (seconds)

  Valid Values: 0 to ??? MAXINT

  Changes Take Effect: ???

  If the GAX and Configuration Server clocks are not synchronized, this option provides the specified time interval (in seconds) as tolerance before the token start'time and after the token end-time.

  For example:

  1. GAX generates a token valid from 12:00:00 to 12:20:00
  2. The token-tolerance option is set to 60s (the default).
  3. On the Configuration Server side, the token is valid from 11:59:00 to 12:21:00.

  token-ttl

  Default value: 1440 (minutes)

  Valid Values: ???

  Changes Take Effect: ???

  Specifies how long (in minutes) the token is valid on the Configuration Server side.

  If the value is set to a positive non-zero integer, the token is valid for the time interval specified by this option, starting from the time specified by GAX. For example:

  1. GAX generates a token which is valid from 12:00 to 3:00.
  2. The token-ttl option is set to 60 minutes.
  3. On the Configuration Server side, the token is valid from 12:00 to 1:00.

  But if token-ttl is set to 65 minutes, the token is valid from 12:00 to 1:05.

  If this option is not set in a Configuration Server or Configuration Server instance, the option value for this instance is taken from the Application that logged in to GAX. For example, if the user logged into GAX as the default application, the value for token-ttl is set to the value of the token_life_in_minutes option in the [general] section of the GAX application. If token_life_in_minutes is not set, or set to 0 (zero), in the GAX application. the the default value (1440 minutes) of token-ttl is used.

  For more information about this token-based authentication feature, refer to the "Secure Communication with Configuration Server" section in the Genesys Administrator Extension Deployment Guide.

To verify that both exist:

1. Start MS SQL Server Management Studio.
2. In the Connect to Server dialog box, specify an MS SQL Server name and administrator credentials to connect to the MS SQL server.
3. In Object Explorer, expand the entry for the MS SQL Server identified in the previous step, then Security, then Logins. The Logins folder should contain an entry for either the Windows account itself, or the group to which that account belongs; for example, <Domain name>\Administrators.
4. To determine if the Windows account is either directly mapped to the database, or has administrative access to all databases, right-click the user's Login to open the Properties dialog box and select Server Roles. Then do one of the following:
   • If sysadmin is checked in the Server Roles list, this Windows account has access to all databases.
   • If sysadmin is not checked, click User Mapping to see if this Windows account is mapped to the appropriate database as db_owner.

If an appropriate Login does not exist, and/or the Login does not have access to the database, do the following steps, as appropriate: