Scribd
Upload
61 views4 pages

CONNECT-REST in Pega

Uploaded by

krishrs2505
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
61 views4 pages

CONNECT-REST in Pega

Uploaded by

krishrs2505
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

CONNECT-REST (Authentication)

What are the different types of authentications allowed as part of connecting to a service
provided?

BASIC Authentication is used to store the external service provided user name and password in
an Authentication profile and refer to the same in the connect rule forms.
OAuth Authentication is a two-step process verification
Step 1: Register the OAuth2.0 Client Registration rule with the service provider Client ID and
Client Secret Key.
Step 2: Retrieve the token using the OAuth Service Provider service.
How does it work?
Connect Service will retrieve the token using the provided Client ID and Client Secret Key, then
the token is passed as part of the actual service call in the header. Token will have an expiry
defined at the service provider end. The majority of Google, AWS, and Facebook products come
with this type of authentication.

How is the SSO Authentication is implemented through SAML Integration?

SSO- Authentication Service is used to log in through windows active directory credentials.

1. Provide Identify Provider Metadata Information that we got from Windows Active
Directory — Entity Identification URL, Login Location and Logout Location. This information
is specific to the Windows Active Directory environment.

2. In the mapping tab, map the information from the SAML fields to the OperatorID Page fields

3. There are two activities that are present — Pre-authentication and Post-authentication
processing activities. In the Post-authentication processing activity, we can perform the
save of the OperatorID Page to save information mapping from the SAML file to the
OperatorID Page.
What is the CORS (Cross-Origin Resource Sharing) Policy?

The Cross-Origin Resource Sharing policy is allowed to define the allowed origins (kind of
whitelisting the IP’s), allowed headers, allowed methods, and credential usage for a specific REST
Service. Map the CORS record to a service rule.

What are the connect and service request processors?

The connect and service request processors are used for the asynchronous processing of
connect-soap or service-soap calls. These are the queue data instances, processed by the PEGA-
Intsvcs agents.

What are the different ways that we can invoke a connector service?

They are three different ways as follows

Run: Synchronous way of invoking a service

The design approach for invocation: In the invoke activity, call the Connect-REST in run mode

Run in Parallel: Create a pool using the Load-DataPage or Call-Async-Activity methods and
execute the multiple service calls in a parallel mode. This execution mode creates the child
requestor from the current requestor.

The design approach for invocation: Use the Connect-Wait method, to wait for all child
requestors to complete processing and merge into the current requestor.

Queue: This mode is for Asynchronous processing.

The design approach for invocation:

Step 1: Create the Connector Requestor instance with the custom System Queue class. Refer to
this instance as the Queue Processing Option in the Connect-REST/Connect-SOAP instance.
Step 2: In the invoke activity, call the Connector service in the Queue mode. As part of the
execution, it will create the System Queue class for processing. Pega-IntSvcs Agent Connector
standard agents process these requests.

Step 3: As part of the case design, invoke this connector in the queue mode. Then place the
assignment in the waiting queue workbasket. Create the advance agent to process the System
Queue class instances with Success status. This advance agent will progress the case to the next
step

How do you configure the Headers connect-rest in pega ?

Each Method on the Request tab of the Connect-REST rule form provides an
opportunity to map Constants - or Clipboard data from your service page - to your REST
request. The below screenshot is from an 8.4 Connect-REST rule that ships with Pega
FFS.
So long as the step page of your Connect-REST call holds the value you want to use for
your Header, it can be mapped into Headers the same as Query String or Message Body
data.

Connect-REST rules also take Parameters that could be used for this purpose

You might also like