Page created: 25 Nov 2020
|
Page updated: 8 Feb 2022
Client Initiated Backchannel Authentication (CIBA) involves prompting a user to accept or reject a request. You can customize the request prompt using pre-defined attributes or map complex custom attributes.
Simple prompt customizations
For simple, centralized customizations, you can modify the notification template that PingOne uses to generate the request prompt.
Notification template customizations allow you to use the following:
- Static text
- A pre-defined set of attributes from the client request context
Simple prompt customizations require changes to the PingOne notification template only.
- Location: .
Advanced prompt customizations
If you need more advanced customizations in the request prompt, you can define custom attributes in PingFederate and pass them to PingOne.
The PingOne MFA CIBA Authenticator allows you to use the following:
- Static text
- Modified attributes from the client request context
- Contract attributes from the PingFederate CIBA request policy
- Messages from the PingFederate language-pack localization files
- Apache Velocity Template Language code to manipulate any of the above
Advanced prompt customizations require coordinated changes to all of the
following:
- The PingOne notification template
- Location: .
- The PingOne Template Variables table of the PingOne MFA CIBA
Authenticator instance
- Location: .
- The Extended Contract tab of the PingOne MFA CIBA Authenticator
instance
- Location: .
- The PingFederate CIBA request policy
- Location: .
For details descriptions and examples, see Advanced CIBA prompt customizations.