Configure the secret key for single sign-on in the analytics configuration file (biConfig.xml)

To configure single sign-on between Management Center and , your biConfig.xml file must define a secret key. This secret key is used to create a token for single sign-on authentication. We must provide your secret key to your IBM Digital Analytics Support representative so that the same key is configured in the IBM Digital Analytics system.


Procedure

  1. Open the workspace_dir\crs-web\WebContent\WEB-INF\xml\config\bi\biConfig.xml file.

  2. Locate the following element: 

      <ssoKey></ssoKey>

  3. Check whether there is already a secret key that is defined in the element. If so, the element would look similar to this example: 

      <ssoKey>2390eabf0795mprs</ssoKey>

    • If there is a key that is already defined, skip to step 6.

    • If the element is empty, define a secret key. We can use any string that we want, but ensure that we define a strong key. For example, use a 16-character string that:

      • Contains at least one letter and one number.

      • Does not contain the same character more than 4 times in a row.

      Example: 

        2390eabf0795mprs

  4. Save and close the file.

  5. Restart test servers.

  6. Provide your secret key to your IBM Digital Analytics representative so that IBM Digital Analytics can configure this key in their system. If IBM Digital Analytics does not have the identical secret key that is configured, then single sign-on does not work. Tip: It is a good practice to change your secret key periodically by changing your entry in the <ssoKey> element in this file and then providing IBM Digital Analytics with the changed secret key.


Next topic: Mapping a WebSphere Commerce user name to a IBM Digital Analytics user name for single sign-on


Related tasks
Configure single sign-on between Management Center and IBM Digital Analytics


Related reference
Troubleshooting single sign-on between Management Center and IBM Digital Analytics