Skip to content

Restricting access using server document access fields

An administrator can define which users are allowed to connect to the HCL Traveler server, or create explicit denial lists for users that should be denied access to the server. In a Traveler HA environment, repeat the procedure on each server in the pool.

The server access depends on the user's identity, so it requires NTS_USER_SESSION set to TRUE (default in HCL Traveler 11 and up). If NTS_USER_SESSION has been explicitly set to FALSE, the server's identity will be used.

  1. From the Domino® Administrator client, select the HCL Traveler server document.

  2. Click Edit Server.

  3. Click the HCL Traveler tab.

  4. Populate either the Access Server or Not Access Server field with the names of users and groups.

Field Description
Access Server Select the option **Users listed in all trusted directories** to allow access to HCL Traveler only to people that have person documents in either the primary directory of this server or any secondary directories that trusted credentials using Domino directory assistance. You can also select individual names of users and groups to allow access to this HCL Traveler server. A blank entry means that all users can access HCL Traveler except any who are listed in the **Not Access Server** field.
Not Access Server Select the names of users and groups that should be denied access to this HCL Traveler server. A blank entry means that no users are denied access. **Note:** Entering names in the **Access Server** field automatically denies access to those names not listed.
  1. Click Save Close.

Note: Users defined as Domino 'Full Access Administrators' have access to HCL Traveler regardless of how the Not Access Server or Access Server fields are configured.

Note: Users denied access to Domino through the Domino Not Access Server or Access Server fields under the Security tab of the server document cannot access HCL Traveler.

Parent topic:Controlling access to HCL Traveler

&