Configure authentication by completing the following tasks.
Configuring Active Directory
To enable NT authentication use by Tealeaf, you must complete the following configuration steps in Active Directory.
- In Active Directory, create two global security groups, one each for users and administrators. For example,
TLuser
andTLadmin
. - Assign Tealeaf users to these groups.
- Tealeaf administrators must be permitted to create events. Access is provided by enabling access to the Event Manager through the Portal menu. Note: Search Server can be configured to use a Tealeaf event-based method for data segmentation. See Configuring the Search Server.
- Verify that the Portal Server has permission to query Active Directory for group information. For more information, refer to your Active Directory documentation.
- A service account must be created or used to run the Search Server service. You must create a new account within Active Directory if the local computer account does not have these rights or if multiple domains are involved.
- Test accounts from both user groups by logging in to the Portal and running a search.
Configuring NT authentication for Search server
To configure NT authentication for the search server, edit the Search Server configuration using TMS in the Portal.
Verify that the Admin and User groups you want to use for the Search Server exist on the NT domain controller that you are using for authentication.
- In the Portal, navigate to TMS.
- In the WorldView tab, drill down to the Search Server component for the desired server.
- Select Search Server configuration and click View.
- Click Edit on the Config Info dialog to edit the configuration.
- In the Authentication area of the Search Config window, click Modify.
- In the Authentication dialog, do the following:
- For Authentication Type, select NT Authentication.
- Select the NT domain to use from the Domains drop-down menu.
To enter another domain, select Enter Domain. In the dialog box, enter the domain identifier.
Note: To specify a child domain, you may need to try both of the following forms:child.domain.com
child
- Click Add to User Groups.
Users who are members of the groups in the User Groups list can use Search Server features such as searching, getting session information, and retrieving sessions. Users who belong to only this group may not configure Canister events.
- The resulting Add Group dialog lists the groups defined on the domain controller for the chosen domain.
- Choose a group from the list and click List Group. A list of members of that group is displayed.
- Click OK to add the group to the list of Search Server user groups. Repeat this step if needed.
- Click Add to Admin Groups.
Only users who belong to this group may configure Canister events and upload shared Viewer profiles.
- The resulting Add Group dialog lists the groups defined on the domain controller for the chosen domain.
- Choose a group from the list and click List Group. A list of members of the group is displayed.
- Click OK to add the group to the list of Search Server user groups. Repeat this step if needed.
- Click OK to close the Authentication dialog.
- Enter a description for the change to the configuration in the Version Description field and click Save.
- When prompted whether to add tasks to push the new version, click Yes. Also select Yes if you want to add restart tasks.
- Enter a description in the Current Job pane, then click Submit to push the changed configuration and restart the Search Server.
- Test the authentication by opening the CX RealiTea Viewer and running a search.
If you are not a member of one of Search server user groups, you are denied access to searching.
Note: If Search Server NT authentication is enabled and the Search Server service is running as a user that is not registered on the NT domain specified in SearchConfig (a member of one of the machine's local user groups), the service fails to start (it may return error code 110). Running the Search Server service under the Local System account is acceptable.
Enabling Portal NT Authentication
To use NT authentication in the Portal, the machine on which the Portal is running must be a member of an NT domain. It should be in the same domain as the NT domain controller, or a trust relationship must be established between the domain controller domain and the Portal server domain.
To enable this feature, you must turn on NT authentication for the Report database and modify IIS settings for the Portal virtual directory.
Note: By default, the Portal creates an "internal" account for every valid NT user in the valid groups.- Log in to Portal as an administrator.
- Navigate to TMS.
- Open the Tealeaf node displayed under Portal server.
- Click Shared configuration information.
- In the Config Actions panel, click View/Edit.
- You will see Tealeaf Report configuration.
- Click the Authentication Method field displayed under the Portal tab.
- You will see an Edit config item screen. Select NT from the drop-down and click Apply.
- Click Save button on the Tealeaf Report Configuration screen.
- When prompted to update server/s, click Add Tasks & Submit.
- If you have a Report server running on a separate machine, repeat the above steps for its configuration as well.
IIS changes to enable Portal NT Authentication
- Open the Internet Information Services Manager from the Windows™ Start menu:
Start > Administrative Tools > IIS Manager. - Expand the machine node and go to Portal virtual directory under the website where it was installed (usually the Default Web Site).
- In the pane on the right, double click Authentication to open its settings.
- Disable Anonymous access and enable Windows authentication.
- Close the dialog.
- Perform an IIS reset and restart all Tealeaf services.
Creating Portal users
Depending on your configuration settings, the Portal can automatically create Portal user accounts for NT users when they first visit the Portal home page. Alternatively, you can create these accounts by mapping them manually.
Automated Portal user creation
You can configure the Portal to automatically create Portal user accounts for NT users that arrive to the Portal login page. You can assign the Portal account to one product (cxImpact, cxView, or cxReveal) and any groups within that product.
Any other product assignments must be completed after the user is created.
Note: To auto-create users across multiple products, you could notify cxImpact users to login Monday and cxView users to login on Wednesday, making the necessary configuration changes between days.
After you have enable NT authentication through Search Server, you must configure settings in each of the product settings groups.
- From the Portal menu, navigate to Portal Management.
- General User Creation Settings:
- Click CX Settings > Users.
- Configure the following settings to the listed values.
Setting Value Automatic NT User Login
Enabled
Automatic User Creation
Enabled
Automatic User Creation Settings Prompt
optional Automatic User Creation Type
Set this value to the Tealeaf product to which you would initially like to assign users. Portal users are cxImpact users. Note: For the product to which you are assigning new users, you must enableAutomatic User Creation
. - Password Security: The following settings pertain to password length, security, and duration. If you have not done so already, consult with your IT staff to determine requirements. To read more about password requirements, please see require strong passwords in Configure CXview settings.
Minimum Password Length
Previous Password History (Count)
Previous Password History (Days)
Require Strong Passwords
- New users must create a password that meets these guidelines
- Click Save.
- cxImpact User Settings: If you chose
Portal
forAutomatic User Creation Type
, complete the following configuration for new users automatically created by the Portal.- In the same settings, configure the following fields to meet your requirements.
New User Default Group
New User Default Page
New User Default Time Zone
New User Group Default Language
- Click Save.
- In the same settings, configure the following fields to meet your requirements.
- cxReveal User Settings: If you chose
cxReveal
forAutomatic User Creation Type
, complete the following configuration for new users automatically created by the Portal.- In the Portal Management page, select cxReveal > Users.
- Configure the following settings to meet your requirements.
Automatic User Creation
must be enabled.New User Default Page
New User Default Time Zone
User Default Group
- You should also review the Password-related settings.
- Click Save.
- cxView User Settings: If you chose
Portal
forAutomatic User Creation Type
, complete the following configuration for new users automatically created by the Portal.- In the Portal Management page, select cxView > Users.
- Configure the following settings to meet your requirements.
Automatic User Creation
must be enabled.Automatic User Creation Settings Prompt
New User Default Page
New User Default Time Zone
User Default Group
- You should also review the Password-related settings.
- Click Save.
Manually mapping Portal users to NT users
To map a Portal user to an NT user:
- Log in to the Portal Web application as a Portal administrative user.
- Navigate to Portal Management.
- Click the user administration link for the type of user you want to create. Note: For cxImpact, select CX User Administration.
- Click Users.
- Click New in the toolbar.
- Enter the Portal username if creating a new user. Enter the NT domain and NT username (exactly as typed by the user when logging into the NT domain) to which this Portal user maps.
- Specify other user properties. Note: Only one Portal user account should be associated with each NT domain/user combination.
- Click Save.
- When the user whose account you just modified requests the Portal login page, their NT username is posted to the login page, and the user can access the Portal by clicking Login.
HTTPS/SSL and NT Authentication
If you use NT Authentication and also turn on HTTPS/SSL on the Portal (in IIS settings), you might not see the expected NT-authenticated login page for the Portal until the Portal machine is added to Internet Explorer's Trusted Intranet Zone.
Note: If you encounter the Portal error The ASP Utility Object (TLAspUtil) could not be loaded, and you have been recently added to the Users Active Directory group, then perform this procedure.- Go to Start > Run.
- Type cmd in the Open field.
- Enter the following command:
gpudate /force
- Reboot the user's machine. Important: It is important to reboot and not simply log off.