Runtime notifications
You can configure PingFederate to generate notification messages for various events.
Complete this configuration on the Runtime Notifications window.
- Licensing events
-
Depending on your licensing agreement, your PingFederate license might have an expiration date. You can configure PingFederate to generate notification messages when your license is about to expire. This option does not appear when you have a perpetual license.
- Certificate events
-
When enabled, PingFederate can generate notification messages when a certificate is about to expire or has expired. If you have also configured PingFederate to rotate self-signed certificates, PingFederate can generate notification messages after generating a certificate and after its activation.
- SAML metadata update events
-
If you have enabled automatic reloading of partner metadata in any SAML browser single sign-on (SSO) connections, you can configure PingFederate to generate notification messages when it detects changes after pulling the metadata from the partners.
- Thread pool exhaustion events
-
When enabled, PingFederate can trigger the logging of a thread dump when the number of threads in use reaches a defined threshold. You can also configure a notification (by email, etc.) to an administrator about these events.
- Thread pool bulkhead events
-
When enabled, PingFederate can log when runtime threads reach their defined bulkhead limits. You can also configure a notification (by email, etc.) to an administrator about these events.
|
In a clustered PingFederate environment, notification messages for licensing and certificate events are generated by only one of the nodes. If that node leaves the cluster, planned or not, another node picks up this task automatically. |
Regardless of runtime notification settings, PingFederate always records license expiration events, certificate events, and SAML metadata update events in the server log. For more information, see PingFederate log files.