Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Enforcing policies from the Security Policies landing page

Suggest edit Updated on July 1, 2021

You can configure your SAML SSO authentication service to enforce security policies that are defined on the Security Policies landing page.

  1. Open the service from the navigation pane in Dev Studio by clicking RecordsSysAdminAuthentication Service and choosing a service from the instance list, and then click the Security policies tab.
  2. Click the Add item icon to specify a security policy.
  3. In the Policy type list, select the policy to enforce.
    Note:
    • If you select Multi-factor authentication, you must map properties such as email address or phone number from the email or SMS receiver account by using the Mapping tab.
    • If you select User consent, the section pyPostAuthConsentScreen is displayed to the user after authentication. You can customize this section.
    • If you select CAPTCHA, the settings on the Security Policies landing page take effect as described below.
      • If you set the value of Enable presentation of CAPTCHA upon initial login to Enabled, the CAPTCHA is displayed for every login.
      • If you set the value of Enable presentation of CAPTCHA upon initial login to Disabled, the CAPTCHA is displayed according to the probability that you set in the Probability that CAPTCHA will be presented upon authentication failure (%) field.
  4. Click Save.
What to do next: Activating your SAML SSO authentication service
  • Previous topic Overriding the service provider settings for a SAML SSO authentication service
  • Next topic Activating your SAML SSO authentication service
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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