Skip to main content


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

Configuring advanced features for an OpenID Connect SSO authentication service

Updated on July 1, 2021

You can fine-tune the interaction of Pega Platform and your OpenID Connect authentication provider by supplying additional parameters.

Before you begin: You must complete the following task before you can update the advanced configuration for an OpenID Connect identity provider: Configuring the identity provider for an OpenID Connect SSO authentication service
  1. Open the service from the navigation panel in Dev Studio by clicking RecordsSysAdminAuthentication Service and choosing a service from the instance list.
  2. On the OpenID Connect tab, expand the Advanced configurations section.
  3. In the Client authentication scheme section, select the authentication scheme.
    • Basic
    • POST
  4. In the Send access token as section, select how to send the access token:
    • Authorization header
    • Query string parameter
  5. In the Secure protocol configuration section, complete the following fields:
    1. In the Lowest allowable SSL/TLS version field, select the lowest allowable SSL or TLS version for communicating with your identity provider.
    2. In the Truststore field, press the Down Arrow and select the truststore record that is used for secure access.
    3. In the Keystore field, press the Down Arrow and select the keystore record that is used for secure access.
  6. Click Save.
  • Previous topic Configuring the identity provider for an OpenID Connect SSO authentication service
  • Next topic Mapping operator information for an OpenID Connect SSO authentication service

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us