Skip to main content


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

Authentication in web embed

Updated on October 21, 2022
Applicable to Cosmos React applications

Authentication ensures that only users and systems with a verified identity use the web embed and that all permitted manipulations of the data occur as the current user identity.

OAuth 2.0

The OAuth 2.0 protocol allows external applications to access Pega Platform REST services by using access tokens.

When you create a web embed, Pega Platform automatically defines an OAuth 2.0 client registration data instance that you can access in the records explorer, in the SecurityOAuth 2.0 Client Registration node.

The client is automatically set up as public. You cannot modify this setting.

For more information, see Creating and configuring an OAuth 2.0 client registration.

Authentication services

Web embed supports the same authentication services as its parent application. If an authentication service is defined in the application, you do not need to define it again for the web embed.

For more information, see Creating an authentication service.

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