LDAP/AD Authentication: Difference between revisions
Line 12: | Line 12: | ||
| | | | ||
{| class="wikitable" style="text-align: left" | {| class="wikitable" style="text-align: left" | ||
!Name !!Description | !Name !!Description | ||
|- | |- | ||
|AuthenticationMethod ||Indicates which authentication method is used. | |AuthenticationMethod ||Indicates which authentication method is used. Alternatives: | ||
*'''1''': Users are authenticated using the passwords in QPR ProcessAnalyzer database. Default value.<br> | |||
*1 | *'''2''': Users are authenticated using the LDAP method by validating the username against a corporate LDAP server.<br> | ||
*2 | *'''3''': Users are authenticated using both methods: if LDAP authentication fails, then logging in will be done using the built-in authentication method. | ||
*3 | |||
|- | |- | ||
|LDAPConnectionString | |LDAPConnectionString | ||
||The IP address for establishing the connection to the LDAP server. Append ''':3268''' to the end of the address if you want to use Global Catalog by default. | ||The IP address for establishing the connection to the LDAP server. Append ''':3268''' to the end of the address if you want to use Global Catalog by default. Format: '''xx.x.xx.xxx''' | ||
|- | |- | ||
|LDAPUserFilter | |LDAPUserFilter | ||
||This string is used by the LDAP library to locate and search the user from corporate LDAP server. | ||This string is used by the LDAP library to locate and search the user from corporate LDAP server. For example '''(&(objectclass=person))''' | ||
|- | |- | ||
|LDAPUserSearchBase | |LDAPUserSearchBase | ||
||The distinguished name of the object at which to start the search. | ||The distinguished name of the object at which to start the search. For example '''dc=local''' | ||
|- | |- | ||
|LDAPUserIdAttributeName | |LDAPUserIdAttributeName | ||
||The user id attribute name. | ||The user id attribute name. For example '''sAMAccountName''' or '''uid''' | ||
|- | |- | ||
|LDAPServerUserName | |LDAPServerUserName | ||
|| LDAP server credentials: the distinguished name of the user. | ||LDAP server credentials: the distinguished name of the user. | ||
|- | |- | ||
|LDAPServerPassword | |LDAPServerPassword | ||
|| LDAP server credentials: the password of the user. | ||LDAP server credentials: the password of the user. | ||
|} | |} | ||
|} <!-- End nested table --> | |} <!-- End nested table --> |
Revision as of 22:43, 3 February 2018
QPR ProcessAnalyzer has the following methods for authenticating users:
- Built-in authentication in which users are authenticated using the username and password in stored in the QPR ProcessAnalyzer database (using the Manage Users dialog).
- LDAP/AD authentication (Lightweight Directory Access Protocol/Active Directory) in which users are authenticated by validating the username against a corporate LDAP or AD server. Note that corresponding users need to be created to the QPR PRocessAnalyzer database before user can login (using the Manage Users dialog).
- Combination of the built-in and the LDAP authentication, in which, if the LDAP method fails, the built-in method is used.
In addition, it is possible to use common QPR authentication between different QPR product web clients.
Configuring Authentication Settings
The authentication method options can be configured in the PA_CONFIGURATION table in the QPR ProcessAnalyzer database. The options relevant for authentication are listed in the following table:
|
All values except for AuthenticationMethod are empty by default.
The authentication method that is currently used is shown in Session Information dialog.
Creating Users for LDAP Autentication
The LDAP authentication can be used in QPR ProcessAnalyzer Pro and QPR ProcessAnalyzer Database. LDAP settings have no effect in QPR ProcessAnalyzer Xpress as it does not use user authentication.
1. Edit the LDAP authentication options of the PA_CONFIGURATION table in the QPR ProcessAnalyzer database, or run the following query to the QPR ProcessAnalyzer database:
UPDATE PA_CONFIGURATION SET CFG_VALUE='<value>' WHERE CFG_KEY='AuthenticationMethod'; UPDATE PA_CONFIGURATION SET CFG_VALUE='<value>' WHERE CFG_KEY='LDAPConnectionString'; UPDATE PA_CONFIGURATION SET CFG_VALUE='<value>' WHERE CFG_KEY='LDAPUserFilter'; UPDATE PA_CONFIGURATION SET CFG_VALUE='<value>' WHERE CFG_KEY='LDAPUserSearchBase'; UPDATE PA_CONFIGURATION SET CFG_VALUE='<value>' WHERE CFG_KEY='LDAPUserIdAttributeName'; UPDATE PA_CONFIGURATION SET CFG_VALUE='<value>' WHERE CFG_KEY='LDAPServerUserName'; UPDATE PA_CONFIGURATION SET CFG_VALUE='<value>' WHERE CFG_KEY='LDAPServerPassword';
- Replace <value> in the script with your own specific LDAP settings. Note that you need to allow built-in authentication at this point, so define the value of AuthenticationMethod to be 1. For more information on the values, see the table above.
2. Log in to QPR ProcessAnalyzer as a user that has All and Administrator rights.
3. Create a new user account in the Manage Users dialog. The username in QPR ProcessAnalyzer must match the LDAP username.
4. To allow users to authenticate using the LDAP method, change the value of AuthenticationMethod in PA_CONFIGURATION table to either 2 (to allow only LDAP authentication) or 3 (to allow also built-in authentication in case the LDAP authentication fails).
Note that if the user (other than an Administrator) has successfully been authenticated using the LDAP method, this user is not able to change his or her own password in QPR ProcessAnalyzer.