Restricted Binding functionality in Case Bearer authorization

---
title: Restricted Binding functionality in Case Bearer authorization
description: Restricted Binding Functionality in Case Bearer Authorization
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/instance-security-hardening-settings/sc-restricted-binding-functionality-in-case-bearer-authorization.html
release: australia
product: Instance Security Hardening Settings
classification: instance-security-hardening-settings
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Architecture, design, and threat modeling, Hardening settings, Platform Security]
---

# Restricted Binding functionality in Case Bearer authorization

Restricted Binding Functionality in Case Bearer Authorization

Use the **glide.oauth.enforce\_restricted\_binding\_for\_ui** system property and enable restricted binding for an OAuth entity to prevent the access tokens generated by that entity from being used for UI calls \(For example, `incident_list.do`\).

When restricted binding is turned off, the access token generated can be used for UI calls regardless of the value of the system property.

When the **glide.oauth.enforce\_restricted\_binding\_for\_ui** system property isn't set to **true** or restricted binding is turned off, a user with the access token to access an API \(for example, a mobile API\) can obtain a session and use it to access other restricted resources on the instance \(for example, `incident_list.do`\).

Ensure that the **glide.oauth.enforce\_restricted\_binding\_for\_ui** property is set to **true**.

## More information

<table id="table_ajc_b43_3kb"><thead><tr><th>

Attribute

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Configuration name

</td><td>

**glide.oauth.enforce\_restricted\_binding\_for\_ui**

</td></tr><tr><td>

Configuration type

</td><td>

System Properties \(/sys\_properties\_list.do\)

</td></tr><tr><td>

Data type

</td><td>

Boolean

</td></tr><tr><td>

Recommended value

</td><td>

true

</td></tr><tr><td>

Default value

</td><td>

true

</td></tr><tr><td>

Fallback value

</td><td>

false

</td></tr><tr><td>

Category

</td><td>

[Architecture, design, and threat modeling](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-architecture-design-threat-molding.md)

</td></tr><tr><td>

Security risk

</td><td>

-   Severity score: 5.0
-   CVSS score: Medium
-   Security risk details: When the **glide.oauth.enforce\_restricted\_binding\_for\_ui** system property isn’t set to **true**, a user with the access token to access an API \(for example, a mobile API\) can obtain a session and use it to access other restricted resources on the instance \(for example, `incident_list.do`\).

</td></tr><tr><td>

Functional impact

</td><td>

When the **glide.oauth.enforce\_restricted\_binding\_for\_ui** system property is set to **true** and restricted binding is enabled for a specific OAuth entity, the access token generated using that entity can't be used for UI calls \(for example, `incident_list.do`\).

</td></tr><tr><td>

Dependencies and prerequisites

</td><td>

None

</td></tr></tbody>
</table>**Parent Topic:**[Architecture, design, and threat modeling](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-architecture-design-threat-molding.md)