Configuring OpenID Connect Authentication
Configuring OpenID Connect Authentication
4 Tasks
45 mins
Release 1
Pega Platform 8.3.1
Pega Platform
8.5
English
Scenario
Front Stage is considering using OpenID Connect to Authenticate Operators.
Pega now supports SSO login with OpenID Connect. You can use Gmail, Facebook, or any other Open ID connect Identity
Providers to log in to the Pega Platform™ application.
To use Gmail credentials to log in to the Pega Platform application, you make configurations on the Google Account and in
the Pega Platform application.
The following table provides the credentials you need to complete the challenge.
Detailed Tasks
7. Here we have to provide the Authorized Domain. Generating a Client ID and Secret Key are mandatory:
Application Name: Enter a name to identify your configuration.
Support Email: Enter your Gmail address. This is displayed automatically.
Scope of Google API: Define the scope (for example, Email, Profile, OpenID).
Authentication Domain: Add your hostname where the Pega Platform application is running. If you are using the
Pega Cloud, the domain name is easy to find and use. If you are using the Pega VM or Personal Edition, then a
change is required in the Tomcat server.xml file to use some domain name for localhost. Instructions are provided at
the end of these exercise instructions. For example, www.pegaopenid.com is the domain in the Tomcat server.xml
file/
8. In the header, click Create Credentials > OAuth Client ID to configure the OAuth client ID.
Note: The Client ID and Client secret key are also accessible on the Create Credentials page.
Configure new Single sign-on (SSO) login in App Studio
Configure new SSO login from App Studio
Tip: Open the Authentication Service rule in Dev Studio if any further configuration changes are required. You can
map required properties on the Mapping tab.
5. Search for the default host and enter an address with .com to act as your domain<Engine name="Catalina"
defaultHost="www.pegaopenid.com">
6. In the same server.xml file, search for host name and give the same name.
<Host name="www.pegaopenid.com"
appBase="webapps"
unpackWARs="true"
autoDeploy="true">
After making changes to the files, you can now access the personal edition with a domain name (no need for the port
number).
http://localhost:8080/prweb -- earlier
http://www.pegaopenid.com/prweb -- after changes to server.xml and hosts file
Confirm your work