Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Creating and configuring an OAuth 1.0 client

Updated on July 1, 2021

Create an OAuth 1.0 client data instance to allow an external application to securely access Pega Platform by using OAuth 1.0.

To obtain the required configuration values, see the API guide of the external application you want to connect to.

  1. In the Dev Studio header, click CreateSecurityOAuth Client.
  2. Enter a short description for your OAuth client data instance.
  3. Enter a name in the OAuth Client field. Begin the name with a letter, and use only alphanumeric characters.
  4. Click Create and open.
  5. In the Provider details section, in the Provider name list, select LinkedIn, Twitter, or Custom.
  6. In the Provider details section, enter the relevant provider URLs in the Request token, Authorization, and Access token fields.
  7. In the Consumer identification section, enter the relevant values for Consumer key, Shared secret key, and Signature method.
  8. Click Save.
  • OAuth 1.0 clients

    The OAuth standard framework enables secure, delegated access to services over HTTPS. OAuth provides tokens (sometimes called "valet keys") that provide access to your data that is hosted by a specific service provider. Each token grants access to a specific site for specific resources, for a defined period of time. A later version of this protocol, OAuth 2.0, uses a different data instance type.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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