Authentication and Session Management

When you use P6 EPPM Web Services, you must authenticate your credentials with the server. The server can be configured to authenticate user credentials using the following methods:

If you select multiple authentication modes, priority is given in the order of the list above, with OWSM being the highest priority and Cookies being the lowest priority. For example, if you select both Username Token Profile and SAML, when a call to P6 EPPM Web Services is made, P6 EPPM will look for authentication information that uses Username Token Profile first and if nothing is found, will then look for authentication information that uses SAML.

OAuth tokens can be included in a P6 EPPM Web Services request (without a login). Therefore if a valid OAuth token is found in a P6 EPPM Web Services request, it will be used for authentication.

Note:

In This Section

Using Username Token Profile for Authentication

Using Oracle Web Services Manager for Authentication

Consuming P6 EPPM Web Services over HTTPS (SSL)

Using SAML Token Profile for Authentication

Using HTTP Cookies for Authentication (On-Premises Only)

Using Resource Owner Password Credential (ROPC) Grant Type

Using JSON Web Token (JWT) Grant Type

Generating the OAuth Access Token

Using OAuth for Authentication and Authorization


Last Published Tuesday, April 1, 2025