Prepare Base64-Encoded Credentials

REST Adapter connections that use OAuth authentication require a Base64-encoded username:password value to request an access token.

How Do I Generate Base64-Encoded Credentials?

Use your organization's approved method to Base64 encode the user name and password in the following format:

username:password

Note:

Base64 is not encryption, it is only an encoding. For production credentials, avoid entering usernames/passwords into public online tools. If you must use an online encoder, use it only for non-production accounts. For production credentials, you should generate the value locally using your organization's approved method.

Which Credentials Do I Need To Encode?

For this accelerator, you need to:

  1. Base64-encode the user name and password of the Primavera P6 EPPM integration user that is used in the access token request of this connection: P6 REST API (using the REST Adapter).
  2. Base64-encode the user name and password of the Primavera Unifier integration user that is used in the access token request of this connection: Primavera Unifier API (using the REST Adapter).

Where Do I Use the Encoded Credentials?

Once you generate the encodings, you can copy and paste the encoded credentials in the appropriate location of your access token request.

These are the two access token requests that need encoded credentials:

  1. In the access token request example in the section, P6 REST API (using the REST Adapter), replace the variable <Base64-encoded-username-and-password> with the Base64-encoded credentials of the Primavera P6 EPPM user name and password.
  2. In the access token request example in the section, Primavera Unifier API (using the REST Adapter), replace the variable <Base64-encoded-username-and-password> with the Base64-encoded credentials of the dedicated Primavera Unifier integration user for that connection.