---
title: Use Identity Provider Attribute as Filter Criteria for SAML
description: Use the Identity Provider \(IDP\) attribute from the Security Assertion Markup Language \(SAML\) response as a filter criteria for authentication policy.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/authentication/use-idp-filter-criteria.html
release: australia
product: Authentication
classification: authentication
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 3
breadcrumb: [Attributes for SAML, Identity Provider Attributes Filter, Filter criteria, Adaptive authentication, Authentication, Access Management]
---

# Use Identity Provider Attribute as Filter Criteria for SAML

Use the Identity Provider \(IDP\) attribute from the Security Assertion Markup Language \(SAML\) response as a filter criteria for authentication policy.

## Before you begin

Role required: adaptive\_auth\_admin

You can create session access policy using policy context \(Pre-Authentication, Post Authentication, multi-factor authentication\) and filter criteria \(Role, Group, IP, Location\) with policy inputs and conditions.

The following procedure shows steps to configure the IdP attribute from the SAML response as a policy input to control authentication in the **Post Authentication Context**, **Multi-factor authentication \(MFA\) Context**, and **Zero Trust - Policy based session access**.

The Okta IDP attributes are as displayed in the following screenshot. You should set the Use in Adaptive Authentication as true to use it in the **Post Authentication Context**, **Multi-factor authentication \(MFA\) Context**, and **Zero Trust - Policy based session access** policies.

\[Omitted image "idp-attributes-okta.png"\] Alt text: Okta Idp attributes

**Note:** Policies in the post-authorization, MFA, Zero Trust - Policy based session access execute after the users enter the credentials or SSO response.

## Procedure

1.  Use of IDP attribute in Post Authentication Policy Context.

    Example: Configuring to enable logins from the Okta IDP attributes if the device is trusted.

    1.  Navigate to **All** > **Adaptive Authentication** > **Auth Policy Contexts** > **Post Authentication Policy Context.**.

    2.  Select **Allow Policy** and open the policy record.

    3.  In the Policy Input, create the Policy Input and Policy Condition.

        -   **Policy Input**: Add **device\_trusted-okta**.

            \[Omitted image "post-auth-idp.png"\] Alt text: Allow Policy - Post authentication

        -   **Policy Conditions**: **device\_trusted-okta** is `trusted` and **Identity Provider** is `okta`.

            \[Omitted image "input-idp-condition.png"\] Alt text: Policy input condition

        Based on this configuration, when the device is trusted from the Okta \(IdP\), then the user is authenticated to the instance.

        For more information on how to create Post Authentication Context with Policy and Condition, see [Post-authentication context](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/authentication/post-auth-context.md).

2.  Use of IDP attribute in MFA Policy Context.

    Example: Configuring to enable MFA from the Okta IDP attributes if the device isn’t trusted.

    1.  Navigate to **All** > **Adaptive Authentication** > **Auth Policy Contexts** > **MFA Authentication Policy Context.**.

    2.  In the Policy Input, create the Policy Input and Policy Condition.

        -   **Policy Input**: Add **device\_trusted-okta**.

            \[Omitted image "input-idp.png"\] Alt text: Policy input

        -   **Policy Conditions**: **device\_trusted-okta** is `not_trusted` and **Identity Provider** is `okta`.

            \[Omitted image "mfa-idp-filter.png"\] Alt text: MFA IDP Filter condition

        Based on this configuration, when the device is not-trusted from the Okta \(IdP\), then the user shown a second factor authentication to log in to the instance.

        For more information on how to create MFA Context with Policy and Condition, see [Multi-factor Authentication context](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/authentication/mfa-auth-context.md).

3.  Use of IDP attribute in Zero Trust - Policy based session access.

    Example: Configuring to reduce the privilege of `Itil` role from Okta IDP attributes if the device isn’t trusted.

    1.  Navigate to **All** > **Zero Trust Access** > **Session Access Role Configurations**.

    2.  Create a Session Access role configuration.

    3.  In the Policy Input, create the Policy Input and Policy Condition.

        -   **Policy Input**: Add **device\_trusted-okta** and **has itil role**.

            \[Omitted image "zta-idp-filter-input.png"\] Alt text: Session Access - IDP Filter

        -   **Policy Conditions**: **device\_trusted-okta** is `not_trusted`, **Identity Provider** is `okta`, and **has itil role** is `true`.

            \[Omitted image "zta-idp-filter-condition.png"\] Alt text: Session Access - IDP condition

        Based on this configuration, when the `itil` user using a device that is not-trusted from the Okta \(IdP\), then the user's privileges are reduced for the logged in session.

        For more information on how to create Zero Trust - Policy based session access with Policy and Condition, see [Zero Trust Access \(ZTA\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/session-access.md).