Skip to main content


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

Configuring a Browser requestor

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

After you create an authentication service, you must associate a Browser requestor and Pega application with an unauthenticated Access Group and ruleset to synchronize customizations of your login screens with your application.

Before you begin: If you have not yet done so, create an authentication service. Your application requires an authentication service for users to securely log in. For more information, see Creating an authentication service.
  1. Creating a new system (on-premises only)
    Note: Pega Cloud clients already have their default system associated with their Browser requestor.

    Create a system to later associate with the Browser requestor. The system identifies a single instance of your Pega Platform occurrence for your unauthenticated operators to access.

    1. In the navigation header of Dev Studio, clickCreateSysAdminSystem.
    2. In the Create System rule form, enter a short description and a system name.
    3. Note the system name for future use.
    4. Click Create and Open.
    5. Click Save.
  2. Associating the system with the Browser requestor (on-premises only)

    Create a new dynamic system setting that associates the new system with the Browser requestor.

    1. In the navigation header of Dev Studio, click CreateSysAdminSystem.
    2. In the Setting Purpose column, click the Search icon.
    3. In the Search Text field, enter prconfig/identification/systemName/default.
    4. Click Apply.
    5. Click the resulting row.
    6. In the Value field, associate the requestor with the system that you created by entering the new system name.
    7. Restart the application server.
  3. Creating an Access Group to associate with the Browser requestor
    Save a copy of the PRPC:Unauthenticated Access Group to maintain its roles for unauthenticated operators.
    1. In the navigation pane of Dev Studio, click RecordsSecurityAccess Group.
    2. In the Access Group Name column, click the Search icon.
    3. In the Search Text field, enter PRPC:Unauthenticated.
    4. Click the resulting row.
    5. In the rule form header, select the list next to the Save button.
    6. Click Save As.
    7. In the Save Access Group As form, enter a short description and a name for the Access Group.
    8. Click Create and Open.
    9. In the Application section of the Access Group rule form, enter the Name and Version of the application you want to customize.
    10. In the Available portals section, select the portal for which you want to customize the login screen HTML and CSS.
    11. Click Save.
  4. Creating an unauthenticated ruleset
    Create a ruleset for an unauthenticated operator to access the Browser requestor session used by the login screens.
    1. In the navigation pane of Dev Studio, click RecordsSysAdminRuleset.
    2. In the Create Ruleset Version field, enter the following information:
      • A ruleset name. Include a hyphen (-) and unauthenticated after the ruleset name, for example: <rulesetname>-unauthenticated
      • The ruleset version. Example: 01-01-01
      • A description for the ruleset.
    3. Note the unauthenticated ruleset name and version for future use.
    4. Click Create, then click Save.
  5. Including the unauthenticated ruleset in your Access Group

    Add the unauthenticated ruleset that contains the unauthenticated Access Group and its composite roles to your application.

    1. In the navigation tabs of Dev Studio, select your unauthenticated Access Group.
    2. In the Run time configuration setting section, in Production Rulesets, add the ruleset that you created.
  6. Adding the ruleset stack to your current application
    Add the unauthenticated ruleset that contains the unauthenticated Access Group and its composite roles to your application.
    1. In the navigation header of Dev Studio, select ConfigureApplicationStructureRuleset Stack.
    2. Select the application for which you want to edit the web login HTML and CSS.
    3. Click Add ruleset.
    4. Add the unauthenticated ruleset that you created to associate with the Browser requestor.
    5. Click Save.
  7. Updating the Browser requestor type
    Update the Browser requestor to use the unauthenticated Access Group.
    1. In the navigation header of Dev Studio, select ConfigureSystemGeneral Requestors.
    2. In the Requestors list, select the Browser requestor that is associated with the system you created.
    3. In the Access Group Name field, enter the Access Group that you created.
    4. Click Save.
What to do next: You associated the Browser requestor with the Pega application and its unauthenticated ruleset, and can now customize the login screens for unauthenticated operators.
  • Previous topic Customizing login screens for your Pega application
  • Next topic Editing the source HTML of your login screen

Related articles

Editing the source HTML of your login screenEditing the text rules containing the source CSS for login screensAdding a new background image to your login screen

Tags

Pega Platform 8.6 User Experience

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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