Skip to main content


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

Mapping operator information for an anonymous authentication service

Updated on March 15, 2022

You can map attributes to selected properties and pages used by your preauthentication and postauthentication activities or by other Pega Platform features such as access control policies. Mapping complements the use of preauthentication and postauthentication activities, operator provisioning by data transform, and other actions.

  1. Open the service from the navigation panel in Dev Studio by clicking RecordsSysAdminAuthentication Service and choosing a service from the instance list.
  2. Click the Mapping tab.
  3. Map the attributes from your login process to properties and pages that are used by your preauthentication and postauthentication activities or elsewhere in Pega Platform.
    1. You can use the following properties and pages in the Map from field. You can also reference custom properties and pages that are used in a login flow, and you can use the Expression Builder.
      Page nameDescription
      pxRequestorThe requestor page
    2. You can use the following properties and pages in the Map to field. You can also reference custom properties and pages that are used in a login flow.
      Page nameDescription
      OperatorIDProperties of the operator ID
      D_pyOperatorAttributesRequestor-scoped data page for caching operator attributes
      D_pyOperatorDeviceInformationRequestor-scoped data page for caching operator device information
  4. Click Save.
  • Previous topic Specifying preauthentication and postauthentication activities for an anonymous authentication service
  • Next topic Activating your anonymous 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