Adding ID DataWeb policy decisions to your authentication policy

Page created: 27 Dec 2019 |

Page updated: 8 Feb 2022

| 2 min read

ID DataWeb Other Documents Integrations Language English Integration Content Type Product documentation Audience Administrator

By modifying your PingFederate authentication policy to include the policy decision ("allow", "obligation", and "deny") from the ID DataWeb API, you can dynamically change authentication requirements based on security risk level.

These steps are designed to help you add to an existing authentication policy. For general information about configuring authentication policies, see Authentication Policies in the PingFederate documentation.

On the PingFederate administrative console, go to the Policies tab.
- For PingFederate 10.1 or later: go to Authentication > Policies > Policies.
- For PingFederate 10.0 or earlier: go to Identity Provider > Authentication Policies > Policies.
Select the IdP Authentication Policies check box.
Open an existing authentication policy, or click Add Policy. See Defining authentication policies in the PingFederate documentation.
In the Policy area, in the Select list, select an ID DataWeb IdP Adapter instance.
Map the user ID into the ID DataWeb IdP Adapter instance.
1. Under the ID DataWeb IdP Adapter instance, click Options.
2. On the Options dialog, from the Source list, select a previous authentication source that collects the user ID.
3. From the Attribute list, select the user ID. Click Done.
Define policy paths based on risk results.
1. Under the ID DataWeb IdP Adapter instance, click Rules.
2. On the Rules dialog, in the Attribute Name list, select policyDecision.
3. In the Condition list, select equal to.
4. In the Value field, enter approve, obligation, or deny.
5. In the Result field, enter a name. This appears as a new policy path that branches from the authentication source.
6. If you want to add more authentication paths, click Add and repeat steps a-e.
7. Click Done.
Configure each of the authentication paths, including Fail, Success, and the paths that you defined in the Rules dialog.

Note: In case the ID DataWeb API is unreachable or returns an error, we recommend that you allow users continue to sign on by satisfying stricter authentication requirements.
You can do this in your authentication policy by setting the Fail outcome of the ID DataWeb IdP Adapter instance to point to a second authentication factor, as shown in the example below.
Alternately, you can do this in your ID DataWeb IdP Adapter instance by setting the Failure mode as shown in Configuring an adapter instance.
Click Done.
In the Policies window, click Save.