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.

Accessing protected API resources by using OAuth 2.0

Updated on September 10, 2021

Leading providers of services for social networking, messaging, file storage, media, health informatics, and the Internet of Things (IoT) publish their data through RESTful APIs that are often protected by the OAuth 2.0 protocol. The Pega 7 Platform acts as a consumer for these REST services and allows you to access OAuth 2.0-protected API resources. You can connect to leading OAuth 2.0 providers such as Box, Twitter, Facebook, and Google by using the authorization code or client credentials grant type.

  1. Reference the OAuth 2.0 Provider data instance and enter the client information from the provider (for example, Box) in an authentication profile, as shown in the following figure:

    Creating an authentication profile

    Creating an authentication profile

  2. Add an external web component section to a layout, a region, another section, or a cell in a layout to handle OAuth 2.0 provider authorization and authentication dialog boxes as shown in the following figures:
     

    Adding an external web component section

 

Configuring an external web component section

Using the Information Mashup section at run time

Using the Information Mashup section at run time

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