---
sourceDocument: Zurich Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/platform-security

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# MFA system properties

# Multi-factor Authentication system properties {#ariaid-title1}

Release version: Zurich  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Multi-factor Authentication system properties

ServiceNow's Multi-factor Authentication (MFA) system properties allow you to enable and customize MFA to enhance your instance's security.
These properties provide control over how MFA is enforced, user experience during setup and login, and support for different authentication methods.
Show full answer Show less  

## Key Features

* **Enable MFA:** Activate MFA for users with `glide.authenticate.multifactor`. You can also enforce MFA for API integrations using `glide.authenticate.multifactor.forintegrations`.
* **Setup Bypass:** Define how many times users can skip MFA setup with `glide.authenticate.multifactor.setup.bypass.count`.
* **One-time Code Validity:** Control the validity period of email-based OTPs using `glide.multifactor.onetime.code.validity` and adjust clock skew tolerance with `glide.authenticate.multifactor.clockskew` to accommodate minor time discrepancies during code validation.
* **Remember This Browser:** Enable users to avoid repeated MFA prompts on trusted browsers with `glide.authenticate.multifactor.remember.browser.enable`. The trusted status duration is customizable via `glide.authenticate.multifactor.browser.fingerprint.validity`, which is based on a browser fingerprint that may require re-authentication if device parameters change.
* **Manage Remembered Browsers:** Limit the number of browsers remembered per user through `glide.authenticate.multifactor.remembered.browser.max.count` and set default selection for the remember-browser option with `glide.authenticate.multifactor.remember.browser.default`.
* **Passwordless Authentication:** Support FIDO2-based MFA methods such as hardware keys and biometric authentication via `glide.webauthn.enabled`.
* **Email OTP Factor:** Enable email-based one-time passwords as a factor with `glide.authenticate.multifactor.email.otp.enable`.
* **UI Flexibility:** Allow users to enable MFA factors without requiring authenticator app setup using `glide.auth.mfa.ui.v2.enabled`.

## Practical Impact for ServiceNow Customers

These system properties provide you with granular control over MFA behavior to balance security and user convenience. You can enforce MFA where needed, customize code validity windows to reduce login errors, and improve user experience by remembering trusted browsers. Additionally, you gain flexibility to adopt modern authentication methods such as passwordless login and email OTPs. Proper configuration helps secure access to your instance while minimizing friction for users, including integrations and APIs.  
Use system properties to enable and customize MFA to meet your security
requirements.
{#mfa-properties__table_lxg_qcz_bs__entry__2}

| Property | Description |
|-|-|
| glide.authenticate.multifactor | Enable Multi-factor Authentication. Note: To enforce MFA for API authentication, set the `glide.authenticate.multifactor.for_integrations` system property to `true`. MFA is enforced only for users who have already enrolled in MFA. Users who have not enrolled are not affected. |
| glide.authenticate.multifactor.setup.bypass.count | Number of times that a user can choose to skip the setup of MFA. The default is 0. |
| glide.multifactor.onetime.code.validity | Number of minutes that the reset code is valid. See [Log in with Multi-factor Authentication](https://www.servicenow.com/docs/Bxjs7S7thEl2KbLkZdmsLA "Login with MFA when it is enabled by your administrator on your instance."). The default is 5. Note: This property is for email OTP validation time. |
| glide.authenticate.multifactor.clock_skew | Number of additional seconds that the reset code is valid. The maximum is <kbd class="ph userinput">60</kbd>. The default is <kbd class="ph userinput">10</kbd>. The instance validates the code entered by the user against the single app-generated code that is generated at the `current time`. You can skew the time window with this property and allow one or more codes to be generated during a time window to be considered valid. The property's value is used in the following calculation: `current time - X/2` and `current time + X/2`, where `X` is the value of this property. If you use the value of `10`, for example, the instance considers any codes that the app generates within the time range `[the current time - 5 seconds]` and `[current time + 5 seconds]` to be valid. Use this property to prevent login issues where the user is unable to enter the correct code in the default time allotted. |
| glide.authenticate.multifactor.remember.browser.enable | Enables "remember this browser" for multi-factor authentication. When enabled, a user who has completed MFA on a given browser or device isn't prompted again on subsequent logins from that same browser or device for the configured time period. The user is prompted for MFA again only when logging in from a new browser or device. Default: true. |
| glide.authenticate.multifactor.browser.fingerprint.validity | Sets how long a remembered browser stays trusted after MFA is completed. Within this period, the user isn't challenged for MFA again in the same browser. Default: 8 hours. Note: Browser trust relies on a browser fingerprint (BFP) --- a hash computed from a set of browser and device parameters. If one of those parameters changes during the validity period --- for example, screen resolution changes when an external monitor is connected or disconnected --- the fingerprint no longer matches the one recorded when MFA was last completed, and the user is challenged for MFA again earlier than the validity period would suggest. |
| glide.authenticate.multifactor.remembered.browser.max.count | The number of browsers MFA remembers for this user. |
| glide.authenticate.multifactor.remember.browser.default | Default value of the remember-browser check box in the validate multi-factor page. |
| glide.webauthn.enabled) | Option to enable passwordless authentication (FIDO2 based MFA) methods such as hardware key and biometric authentication. |
| glide.authenticate.multifactor.email.otp.enable | Option to enable email based OTP as a factor for MFA. |
| glide.auth.mfa.ui.v2.enabled | Option to enable MFA factor independently for the users without setting up an authenticator app. |
[Table 1. Multi-factor Authentication properties]

{#mfa-properties__table_lxg_qcz_bs}

