Specifying preauthentication and postauthentication activities for an anonymous authentication service
You can write activities that are triggered at various points during the process of setting up the anonymous operator.
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.
Open the service from the navigation panel in Dev Studio by clickingand choosing a service from the instance list.
On the Anonymous tab, expand the Advanced configuration settings section.
In the Pre-authentication activity field, enter the name of the preauthentication activity.
In the Post-authentication activity field, enter the name of the postauthentication activity.
- Authentication services
To override or extend the default authentication process, create and configure an authentication service.
- More about authentication services
This page describes additional topics relevant to authentication services that are not directly referenced on the rule form.
- Configuring an anonymous authentication service
After you create an anonymous authentication service, configure it so that Pega Platform can support guest users. You can map attributes from the model operator to properties in Pega Platform, and also configure preauthentication and postauthentication activities.
A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.