PingFederate delivers messages to administrators and end users based on notification publisher settings. Each component that is capable of triggering or handling events may use a different notification publisher instance to deliver its messages. For example, you may select an SMTP Notification Publisher instance to deliver messages to your end users in an HTML Form Adapter instance and another SMTP Notification Publisher instance to deliver licensing messages to your fellow administrators.

When a component is configured to deliver its messages based on an SMTP Notification Publisher instance configuration, PingFederate creates notification messages based on template files located in the <pf_install>/pingfederate/server/default/conf/template/mail-notifications directory. Each template file is a combination of variables and HTML codes. As needed, you can modify these template files in a text editor to suit the particular branding requirements.

Note:

If you have a clustered PingFederate environment, copy the customized templates to each node.

Tip:

You may also configure a component to use an Amazon SNS Notification Publisher instance to deliver notification messages. If so, refer to Configuring an Amazon SNS Notification Publisher instance and Event types and variables for more information about this messaging model and the handling of notification messages.