Chat now with support
Chat with Support

Stat 6.1 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: Stat Web Services Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

LDAP Connection Maintenance

For customer sites that maintain LDAP user directories, Stat supports authenticating login credentials based on a user’s LDAP password rather than the default password defined directly in Stat. This allows sites that maintain a large number of user accounts to avoid maintaining an additional set of Stat-specific passwords. LDAP-enabled users can login to both the Stat Windows Client and the Stat Web Client and have their accounts authenticated with their LDAP passwords.

You configure LDAP domains in Stat by specifying the LDAP server parameters, including location, port numbers and the base DN paths used to search for user account directories. After specifying the base DN, you then specify a template DN which will be used to pre-populate the DN for individual users in the User Maintenance table. You can also use the template DN to test the connection between Stat and the LDAP server.

After configuring LDAP domains in Stat and assigning them to users, you “turn on” LDAP by selecting the Enable LDAP option in the System Maintenance table, Other Options tab, as described in the section Other Options Tab .

Stat supports encrypting communication between Stat and the LDAP server by enabling SSL.

LDAP connection security is controlled by the following user class rights:

The LDAP Connection Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Security Settings | LDAP Connect.

Defining LDAP Domains

Click New to create a new LDAP domain.
In the LDAP Cd field, enter a code that uniquely identifies the LDAP domain.
In the Description field, enter a short description of the LDAP domain.
In the Host field, enter the network name that identifies the host machine on which the LDAP server is installed.
In the Ports field, enter the port number of the LDAP server.
In the Base DN field, enter the DN path used to search for users.
In the Test Connect DN field, enter the DN of a valid LDAP account.
Select Append Base DN to append the base DN with the test connect DN.
Click Test Connect.
In the Template DN field, specify the default user DN value.
Stat allows you to use variables for First Name and Last Name fields so that the default value is dynamically applied to each user account, for example: "CN=%first_name%_%last_name%,OU=Employees"
Select Append Base DN to append the base DN with the template DN.
(Optional) If your site is equipped to use SSL and you want to use it to encrypt communication between Stat and the LDAP server, select SSL. Then specify the location of the SSL keystore for the Stat Windows Client or the Stat Web Client:
As an alternative, you can rely on your $JAVA_HOME/jre/lib/security/jssecacerts keystore to provide the certificate for your LDAP server. In this case, you can leave the Keystore Location field blank provided that jssecacerts exists in the Windows client jre/lib/security directory and that jssecacerts contains the LDAP certificate. For the Stat Central Agent, you can leave the Agent Keystore field blank provided that jssecacerts exists in the Central Agent's jre/lib/security directory and that jssecacerts contains the LDAP certificate.
Click OK or Apply to save your work.

Assigning LDAP Domains to Users

Click Update User DN.
This updates the user’s DN by appending the selected LDAP domain’s Base DN to the Template DN. It also automatically selects the Enable LDAP option. When you update a user’s DN, it automatically updates the user’s DN in the User Maintenance table as well.
Click OK or Apply to save your changes.

Connection Manager

The maximum number of active users (meaning users who can connect to Stat as specified in the User Maintenance table) equals the number of licensed seats. Once the number of active users equals the number stipulated in the license agreement, new user connections are denied.

The Connection Manager window displays a list of all the users currently connected to Stat as well as a record of denied and terminated connections. From this window you can manually disconnect users from the Stat Repository, thereby opening seats and allowing other users to connect.

Connection Manager security is controlled by the user class right, Database Connections - Manage.

To open the Connection Manager window, select Maintenance | Security Settings | Connections.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating