Skip to main content

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

Creating a Google authentication service

Updated on June 30, 2021

Create a Google SSO authentication service so that users can authenticate using Google as the identity provider.

Before you begin: To create an authentication service, you must have the pzCanCreateAuthService privilege, which is included in the PegaRULES:SecurityAdministrator role.

Before you create a Google authentication service, you must register with the identity provider and obtain a client ID and client secret. You do this outside of Pega Platform.

This is a quick way to define an authentication service with Google as the OIDC provider. The result is the same as creating an OIDC authentication service and manually specifying the values needed for Google.
  1. In the navigation pane of App Studio, click UsersSingle sign-on (SSO).
  2. Click New, and then click Google.
  3. Enter a Name for the service.
    Result: The value that you enter is used to populate the Login URL field. Users access this URL to log in to your application.
  4. Optional: The Client ID and Client secret field default to the values that you used to log in. If you need different values, enter the values that were assigned by your identity provider.
  5. Optional: To automatically create an operator when the operator who is logging in does not already exist in the Pega database, do the following steps.
    1. Select the Create operators for new users check box.
    2. In the Access role list, click the access role for the new user.
  6. Click Submit.
  7. To enable the authentication service, on the Single sign-on (SSO) landing page, where the new service is listed, turn on the switch.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us