By default, all P6 EPPM applications use Native authentication. After you install your P6 EPPM applications, you can choose a different authentication scheme.
Note: If you are upgrading from a previous version of P6 EPPM, see the Automatically Upgrading and Configuring P6 EPPM guide before modifying the authentication settings.
Your database instance controls your Authentication mode, which means you can enable a different authentication mode for each of your configurations.
If using Single Sign-On authentication, you can set P6 to SSO but set P6 Professional and P6 Integration API to LDAP. When using SSO mode, P6 Integration API uses LDAP mode.
If using LDAP authentication, you can specify LDAP servers, configure more than one LDAP server for each database instance, map LDAP attributes to P6 EPPM database fields, and provision users.
Follow the guidelines below to specify an authentication scheme and perform additional configuration tasks for authentication:
Configure BI Publisher to use with P6 when using LDAP or SSO mode. See the Connecting BI Publisher to P6 guide for more information.
Tips
If multiple instances within a configuration point to the same database, P6 EPPM will use the Authentication Mode for the first instance in the list.
To enable you to configure more than one LDAP server for each database instance, you can set multiple LDAP Connection Settings for authentication. Right-click the LDAP Connection Settings folder to duplicate, delete, copy, paste, or test a configuration. When P6 authenticates a user, it will search each LDAP server in order for a user name that matches the login name and will use the first matching user to verify the password.
A configuration for P6 might include database instances that are not set to the same authentication mode as the P6 server. If a user connects and requests a database that is set to a different authentication mode than the P6 server, an error message will display; the user must select a database that matches the authentication mode set for the P6 server.