
Configuring OpenID Connect authentication using App Studio
3 Tasks
1 hr
Pega Platform '24.2
Advanced
Pega Platform '24.2
English
Scenario
MDC is considering using OpenID Connect to authenticate operators. As a Lead System Architect, your task is to design and implement an OpenID Connect authentication as a proof of concept.
Pega Platform™ supports single sign-on (SSO) with OpenID Connect. You can use Gmail, Facebook, or any other OpenID Connect identity providers to log in to the Pega Platform application.
There are many identity providers (IdPs) that are available in the marketplace; some are free services while others charge per user. Before MDC decides on an identity provider, they ask you to develop a proof of concept with Okta as the IdP. Okta is a leading IdP that offers secure and scalable identity management solutions. When integrated with Pega Platform for business process management and customer engagement, Okta provides seamless authentication and authorization services. This integration enhances security by enabling SSO for Pega applications.
The following table provides the credentials you need to complete the challenge:
Role | User name | Password |
---|---|---|
Admin | admin@deliveryservice | rules |
Before you begin:
- Register on the Okta developer site.
- On the Okta developer homepage, click Sign up, and then click Sign up free for Developer Edition.
Note: It is free to test, explore, and manage integrations.
- Create an Okta Developer Edition Service account.
- Complete the sign-up process.
Detailed Tasks
1 Configure Okta as the identity provider
- Log in to the Okta Admin Console.
- In the navigation pane, click Applications > Applications, and then click Create App Integration.
- On the Create a new app integration landing page, in the Sing-in method section, select OIDC – OpenID Connect.
- In the Application Type section, select Web Application.
- Next.
- Complete the General Settings section:
- In the App integration name field, enter MDC Web App.
- In the Grant type section, select the following checkboxes:
- Client Credential
- Authorization Code
- Refresh Token
- In the Assignments section, configure the access control options:
- In the Controlled access section, select Allow everyone in your organization to access.
- In the Enable immediate access (Recommended) section, clear the Enable immediate access with Federation Broker Mode checkbox.
- Click Save.
- In the navigation pane, click Directory > People, and then click Add person.
- In the Add person dialog box, configure the user details:
- In the User type list, select User
- In the First name field, enter MDC.
- In the Last name filed, enter POC.
- In the Username field, enter [email protected].
- In the Primary email filed, enter [email protected].
- Leave the Groups (optional) field empty.
- In the Activation list, select Activate now.
Note: You can either set a password for the user or allow Okta to generate a temporary password. If you choose to set the password, you can do so in the provided fields.
- In the navigation pane, click Applications > Applications, and then open the MDC Web App that you created.
- On the Assignments tab, click Assign to select the users or groups who should have access to the MDC Web App application.
2 Create the new SSO in App Studio
- In the Pega Platform instance for the challenge, enter the following credentials:
- In the User name field, enter admin@deliveryservice.
- In the Password field, enter rules.
- In the header of Dev Studio, click Dev Studio > App Studio.
- In the navigation pane of App Studio, click Users.
- Click Authentication. [COE Review: The figure is confusing with the callout around App Studio because they are now two steps beyond that action. I think you can remove the screenshot altogether because, at this point, learners on the LSA track should know how to navigate in App Studio by now.]
- Click Add authentication service, and then, in the list, select Create new > OIDC.
- In the Name field, enter OpenIDPOC.
- In the Create new single sign-on (OpenID Connect) window, click Import metadata, and then enter the URL of okta (https://dev-87031703-admin.okta.com/.well-known/openid-configuration).
Note: You must replace the hostname with your Okta admin registration.
- Click Submit.
- Return to the Otka Admin Console, and then, on the General tab, copy the client ID and client secrets.
- Return to App Studio, and then complete the configuration in the Create new single sign-on (OpenID Connect) window:
- In the Client ID field, enter the details that you captured from Okta Admin Console in step 7.
- In the Client secret field, enter the details that you captured from Okta Admin Console in step 7. [COE Review: Consider removing this screenshot; the screenshot after step 12f better serves the sequence of steps by showing the completed values. To that end, it is also better to remove the callouts.]
- In the Map operator ID from claim field, enter {email}.
- Select Create operators for new users check box.
- In the Access role list, select DeliveryService:Authors.
- Click Submit.
- Confirm that the new OpenIDPOC authentication service Rule is displayed with an Enabled status:
3 Set Pega as the service provider
- In the header of App Studio, click App Studio > Dev Studio.
- Search for and open the OpenIDPOC authentication service Rule.
- In the Redirect URI field, copy the value for the OpenID Connect authentication service.
- Return to the Okta Admin Console, click Applications > Applications, and then open the MDC Web App application.
- In the General Settings section, click Edit.
- Update the sign-in and sign-out redirect URIs with the Pega Platform redirect URI that you captured in step 3.
Confirm your work
- Return to Dev Studio, and then, in the OpenIDPOCCopy authentication service Rule, copy the login URL.
- Open a different browser (if you are using Chrome, open Firefox).
- Paste the login URL into the Web browser.
- Click Login with OpenIDPOC, and then enter your Okta user credentials.
After you sign in, the system automatically creates the Operator ID instance for [email protected] and assigns the ID with the selected Access Role, as shown in the following figure:
Available in the following missions:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?