LDAP/AD Authentication: Difference between revisions
Jump to navigation
Jump to search
(306160) |
No edit summary |
||
Line 5: | Line 5: | ||
== Configuring the Authentication Settings == | == Configuring the Authentication Settings == | ||
The authentication method options can be configured in the PA_CONFIGURATION table in the QPR ProcessAnalyzer database. | The authentication method options can be configured in the PA_CONFIGURATION table in the QPR ProcessAnalyzer database. The relevant options are listed in the following table: | ||
<!-- Begin nested table --> | |||
{| | |||
| | |||
{| class="wikitable" style="text-align: left" | |||
!Name !!Description!!Value | |||
|- | |||
|AuthenticationMethod ||Indicates which authentication method is used. | |||
||*1 = The user is authenticated against the passwords in QPR ProcessAnalyzer database.<br> | |||
*2 = The user is authenticated using the LDAP method by validating the username against a corporate LDAP server.<br> | |||
*3 = The user is authenticated using both methods: if LDAP authentication fails, then logging in will be done using the built-in authentication method. | |||
|- | |||
|LDAPConnectionString | |||
||The IP address of the LDAP server. || | |||
|- | |||
|LDAPUserFilter | |||
||This string is used by the LDAP library to locate and search the user from corporate LDAP server. | |||
|| | |||
|- | |||
|LDAPUserSearchBase | |||
||The distinguished name of the object at which to start the search. || | |||
|- | |||
|LDAPUserIdAttributeName | |||
||The user id attribute name. || | |||
|- | |||
|LDAPServerUserName | |||
||The distinguished name of the user. | |||
|| | |||
|- | |||
|LDAPServerPassword | |||
||The password of the user. | |||
|| | |||
|- | |||
|SandboxDatabaseConnectionString || ||If set, defines the connection string to ETL sandbox database. If not defined, running ETL scripts is not possible. | |||
|- | |||
|AllowNonTemporaryETLTargetTable | |||
||false ||Are ETL scripts allowed to create global temporary database tables (tables starting with ##). | |||
|- | |||
|DatabaseBulkCopyTimeout | |||
||600 ||BulkCopyTimeout given for non-sandbox SqlBulkCopy operations. | |||
|- | |||
|DatabaseBulkCopyBatchSize | |||
||5000 ||BulkCopyBatchSize given for non-sandbox SqlBulkCopy operations. | |||
|- | |||
|SandboxDatabaseBulkCopyTimeout | |||
||600 ||BulkCopyTimeout given for sandbox SqlBulkCopy operations. | |||
|- | |||
|SandboxDatabaseBulkCopyBatchSize | |||
||5000 ||BulkCopyBatchSize given for sandbox SqlBulkCopy operations. | |||
|- | |||
|DeleteModelsInRecycleBinOnStartup ||0 ||If set to non-zero and a client connects to the database, core will automatically launch a background thread that will start deleting models and projects that have been moved to recycle bin (non-permanently deleted). | |||
|} | |||
|} <!-- End nested table --> |
Revision as of 12:42, 28 October 2014
QPR ProcessAnalyzer uses two methods for authenticating users:
- the built-in authentication method in which the user is authenticated against the passwords in QPR ProcessAnalyzer database
- the LDAP (Lightweight Directory Access Protocol) authentication method in which the user is authenticated by validating the username against a corporate LDAP server
Configuring the Authentication Settings
The authentication method options can be configured in the PA_CONFIGURATION table in the QPR ProcessAnalyzer database. The relevant options are listed in the following table:
|