Page created: 13 May 2020 |
Page updated: 8 Feb 2022
Configure the One-Time Passcode IdP Adapter to allow PingFederate to use notification publishers to send one-time passcodes to users during sign on.
- Sign on to the PingFederate administrative console.
- On the Create New Instance. tab, click
On the Type tab, set the basic adapter instance
- In the Instance Name field, enter a name for the adapter instance.
- In the Instance ID field, enter a unique identifier for the adapter instance.
- In the Type list, select One-Time Passcode IdP Adapter. Click Next.
On the IdP Adapter tab, in the Notification
Delivery Methods section, configure a list of delivery methods by
assigning contact information and message templates to your notification
- Click Add a new row to 'Notification Delivery Methods'.
- From the Notification Publisher list, select the notification publisher that you want to use.
In the Contact Attribute list, enter the attribute
that contains the user's contact information for this delivery method. For
- In the Language Properties and Templates Key field, enter a key. For an explanation of keys, see Language property and template keys.
- In the Action column, click Update.
- To add more delivery methods, repeat steps a-e.
- Change the order of the delivery methods to define the sequence that the adapter attempts the deliveries when Device Selection is set to Automatic.
- Configure the adapter instance by referring to One-Time Passcode IdP Adapter settings reference. Click Next.
- On the Actions tab, test your connection to the database. Resolve any issues that are reported, and then click Next.
- On the Extended Contract tab, add any attributes that you expect to retrieve in addition to the core contract attributes. Click Next.
- Complete the adapter configuration.
- On the Summary tab, check that the configuration is correct. Click Done.
- On the Manage IdP Adapter Instances tab, click Save.
- Modify your PingFederate authentication policy to include your One-Time Passcode IdP Adapter instance. Position it after a first-factor authentication step, such as the HTML Form IdP Adapter. For general information about configuring authentication policies, see Policies in the PingFederate documentation.