Skip to main content


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

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.

Specifying preauthentication and postauthentication activities for an anonymous authentication service

Updated on July 1, 2021

You can write activities that are triggered at various points during the process of setting up the anonymous operator.

  1. Create your preauthentication and postauthentication activities.
    For an anonymous authentication service:
    • The preauthentication activity is run before the anonymous operator is populated from the model operator or data transform. It must be accessible to the default access group for the pega Browser requestor type, as described in Authentication services and rule availability.
    • The postauthentication activity is run after the anonymous operator is populated from the model operator or data transform, and affects the anonymous session.
  2. Open the service from the navigation panel in Dev Studio by clicking RecordsSysAdminAuthentication Service and choosing a service from the instance list.
  3. On the Anonymous tab, expand the Advanced configuration settings section.
  4. In the Pre-authentication activity field, enter the name of the preauthentication activity.
  5. In the Post-authentication activity field, enter the name of the postauthentication activity.
  6. Click Save.
  • Previous topic Configuring the anonymous operator for an anonymous authentication service
  • Next topic Mapping operator information for an 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