Page created: 18 Feb 2022
|
Page updated: 10 May 2023
Follow these steps to start using PingOne Risk as part of your authentication flows.
The main steps required to start using PingOne Risk are:
- Integrate with PingFederate or create a worker application.
- Add risk evaluation to your authentication flow.
- Send transaction feedback.
- Configure a risk policy.Note:
If you skip this step, whenever you perform risk evaluation, the default risk policy will be used. You can also edit the default risk policy.
There are three ways to integrate your risk policy into an authentication flow:
- Using the integration with PingFederate
- Building a custom flow with PingOne DaVinci
- Using the PingOne API
These sections spell out the specific steps to carry out for each of these risk evaluation integration routes.
Getting started with PingOne Risk - using PingFederate
Page created: 22 Mar 2022
|
Page updated: 10 May 2023
Configure risk-based authentication using PingFederate as the IdP.
PingFederate must be installed. For help installing PingFederate, see Installing PingFederate.
Getting started with PingOne Risk - creating flow with DaVinci
Page created: 22 Mar 2022
|
Page updated: 10 May 2023
- Configure a risk policy. See Risk policies.
- After you have added DaVinci to your PingOne environment, any risk connectors you add to your flows already have been configured with the correct information for environment ID, client ID, and client secret. However, if you import a flow from a different PingOne environment, you must go to the settings for the risk connector and update this information to reflect the environment where you are adding the flow.
-
Add the following risk elements to your flow by following the directions in the
documentation for the PingOne Risk Connector.
Getting started with PingOne Risk - using PingOne API
Page created: 22 Mar 2022
|
Page updated: 10 May 2023