Page created: 14 Sep 2020
|
Page updated: 16 Feb 2022
Build and deploy a simple example of a custom authentication policy in PingFederate when there are multiple user types that need different authentication flows.
Make sure you have the following:
- PingFederate 10 or later with administrator access to web console
- PingID for multi-factor authentication (MFA)
- HTML Form identity provider (IdP) adapter
- Simple password credential validator (PCV)
- A second SimpleForm (HTML Form adapter) instead of PingID
- IdP connection
- Selector
Authentication policies are an optional configuration in PingFederate and help administrators implement complex authentication requirements.
A simple example of a custom authentication policy is having PingID act as a second-factor authentication event that triggers after a username and password form.
Note:
Consider a custom policy when there are multiple user types that need different authentication flows, or if you want to chain together two types of authenticators, such as username and password with MFA.