Skip to main content


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

Configuring the browser requestor

Updated on February 7, 2022

By associating a browser requestor and your application with an unauthenticated access group and ruleset, you enable customization of your login screens. When you define an unauthenticated access group in the browser requestor form, you give unauthenticated users access to the login screens of your application.

Before you begin: Configure an authentication service. For more information, see Creating an authentication service.
  1. Create an access group with roles for unauthenticated users:

    1. In the navigation pane of Dev Studio, click RecordsSecurityAccess Group.

    2. In the Access Group Name column, click the Filter icon.

    3. In the Search Text field, enter PRPC:Unauthenticated.

    4. Click the resulting row.

    5. In the rule form header, in the list next to the Save button, click Save As.

    6. On the Save Access Group As form, enter a short description and a name for the access group, for example Unauthenticated.

    7. Click Create and Open.

    8. In the Application section of the Access Group rule form, enter the Name and Version of the application that you want to customize.

    9. In the Available portals section, select the portal for which you want to customize the login screen HTML and CSS.

    10. Click Save.

  2. Create an application ruleset to hold the additional rules available for unauthenticated users:

    1. In the header of Dev Studio, click CreateSysAdminRuleSet.

    2. On the Create Ruleset Version form, enter the following information:

      • A ruleset name. Include a hyphen (-) and unauthenticated after the ruleset name, for example: <MyCorpSplash>-unauthenticated
      • The ruleset version, for example: 01-01-01
      • A description for the ruleset.
      Note: For security reasons, do not use an existing ruleset that contains other parts of your application to hold the additional rules for unauthenticated users.
    3. Note the unauthenticated ruleset name and version for future use.

    4. Click Create and open, and then click Save.

  3. Add the unauthenticated ruleset that you created in step 2 to the unauthenticated access group instance that you created in step 1:

    1. In the navigation pane of Dev Studio, click RecordsSecurityAccess Group.

    2. On the Access Group tab, select your unauthenticated access group by clicking the access group name.

    3. On the Advanced tab of the selected access group form, in the Run time configuration section, in the Production Rulesets setting, add the ruleset that you created.

    4. Click Save.

  4. Add the unauthenticated ruleset that contains the unauthenticated access group to your application:

    1. In the header of Dev Studio, select ConfigureApplicationStructureRuleset Stack.

    2. Select the application for which you want to edit the web login HTML and CSS by clicking the application name.

    3. On the Definition tab of the application, click Add ruleset.

    4. Add the unauthenticated ruleset that you created to associate with the browser requestor.

    5. Click Save.

  5. Update the browser requestor type to use the unauthenticated access group:

    1. In the header of Dev Studio, select ConfigureSystemGeneralRequestors.

    2. In the Requestors list, select the browser requestor type that is associated with the system that you created.

    3. In the Access Group Name field, enter the access group that you created.

    4. Click Save.

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