Skip to main content

Configuring an OAuth 1.0a authentication profile

Suggest edit Updated on July 1, 2021

Configure an OAuth 1.0a authentication profile so that messages are sent to and from your application by using OAuth 1.0. To learn how to obtain the values that are needed for the fields on this tab, consult the API guide of the external application to connect to.

Before you begin: You must complete the following task before you can configure an authentication profile: Creating an authentication profile.
  1. Open an authentication profile from the navigation panel by clicking RecordsSecurityAuthentication Profile and selecting an OAuth 1.0a profile from the instance list.
  2. In the Provider details section, enter the details of the OAuth 1.0 provider.
    1. In the Provider name list, select the OAuth 1.0 provider.
      The system generates the values for the rest of the fields in this step according to your selection.
    2. In the Request token URL field, enter the URL that is specified in the API guide of the external application that you want to connect to.
      You access this URL to obtain a request token.
    3. In the Authorization URL field, enter the URL that is specified in the API guide of the external application.
      You use this URL to obtain authorization from the external application by using the request token.
    4. In the Access token URL field, enter the URL that is specified in the API guide of the external application.
      You access this URL to obtain an access token. You can access private resources in the external application by using this token.
  3. In the Consumer identification section, enter additional details that you require to access private resources in the external application that supports OAuth 1.0.
    1. In the Consumer key field, enter the consumer key that is provided by the external application.
    2. In the Shared secret key field, enter the consumer secret that is provided by the external application.
    3. In the Signature method list, select the signature method to sign the request to the external application.
      • HMACsha1 computes a hash-based message authentication code (HMAC) by using the SHA1 hash function.
      • PLAINTEXT computes a text-based message authentication code.
  4. Click Save.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us