Changing the Session Provider

The grid comes with a built-in session provider, the developer session provider, that accepts all users and passwords. Do not use this session provider in a production scenario!

When first installed, the grid has no active session provider. Therefore, you can only get grid-admin access to the grid by using certificate logon, for example by using the AdminUI.cmd script. Alternatively, you can access the HTML-based Grid Management Pages with an appropriate certificate, see Authenticating with a Grid Client Certificate. After getting access as grid-admin, you can change the session provider.

To define a session provider

  1. Install an application that can act as a session provider, that is, provides services according to the SessionProvider interface hierarchy.
  2. Grant session provider rights to the selected application from the grid Configuration Manager.
    1. On the Configuration Manager page, click the Security link and then the Session Providers link.

      The Session Providers page will appear. It displays information about the registered session provider and contains a drop-down list of eligible applications. Of these applications, two are pre-populated entries: "No Session Provider" and "The Developer Session Provider, intrinsic to the grid."

    2. Select the preferred application and click the Grant button.
    3. Save the configuration changes by clicking the diskette icon at the top left corner of the page.

      Note that the changes are applied immediately, and the Session Providers page is updated to reflect the new configuration.

Note: There might be a perceived discrepancy between the Registered Session Provider field and the Application granted Session Provider rights field on the page. The latter can contain more entries than the first. This is because when you register a session provider, you are actually registering an application type (the name in between the parentheses in the drop-down list), not a deployed application instance. You will notice this behavior if you have an application type that is deployed multiple times under different names. The result is that all the instances will be granted session provider rights as indicated under the Application granted Session Provider rights field.