After adding an External web component section, you can configure the section with an OAuth 2.0 authentication profile, mashup section, and authorization section to connect to an external application at run time.
Click the View properties icon for the section to display the Cell Properties panel.
Complete the General tab. For more information, see Presentation Tab.
Complete the Presentation Tab.
On the Parameters tab, complete the Mashup content section to provide the information that allows you to access OAuth 2.0-protected resources on the external application at run time by performing the following actions:
In the Authentication profile field, enter or create an authentication profile of type OAuth 2.0 that you want to use to connect to the external application.
In the Use section field, enter or create a section that displays the OAuth 2.0-protected content of the external application at run time.
In the Page context field, select the page context for the section that displays the OAuth 2.0-protected content at run time. Select the current page context to use the class ( Applies To key part) of the current section. You can also use a data page, clipboard page or a page that is defined by a property.
In the Use section field under Authorization content, enter or create a section that allows you to connect to or disconnect from the external application at run time. The default section is pxMashupAuthorization.
- Presentation Tab
Harness and Section forms - Adding a section
- Creating an External web component
You can add an external web component section to a layout, a region, another section, or a cell in a layout. At run time, this section allows you to connect to external applications and delegate access to OAuth 2.0-protected resources. For example, users can log on to Facebook from Pega Platform by using this section and access photographs in thei
- Authentication profiles
Create an authentication profile to move messages securely to and from your application with a variety of connector and server rules.
- OAuth 2.0 providers
The OAuth 2.0 protocol provides your application with secure authentication in open networks with external applications, such as Facebook, and Google, over HTTPS. You define OAuth 2.0 provider data instances so that Pega Platform can access protected external resources by using access tokens.
A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.
Organize the content and structure of a portal by defining harnesses. By populating harnesses with sections, you can build a modular interface that promotes reuse and maintainability.
Use sections in conjunction with harnesses to define the appearance of user forms, rule forms, or composite portals.