---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security
Release :
- brazil
ft:locale :
- en-US
ft:publication_title :
- Brazil Platform security
ft:clusterId :
- psec
bundleId :
- psec
workflow :
- Platform
---
# MFA system properties
# Multi-factor Authentication system properties {#ariaid-title1}
Release version: Brazil
Updated September 10, 2026
 2 minutes to read
Summarize
 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 provides system properties to configure and customize Multi-factor Authentication (MFA) to enhance your instance's security.
These properties allow you to enable MFA, adjust validation timings, manage browser trust settings, and support different authentication methods including passwordless and email OTP.
Show full answer Show less
## Key Features
* **Enable MFA:** Activate MFA globally or specifically for API integrations. MFA enforcement applies only to users already enrolled, leaving non-enrolled users unaffected.
* **Setup Bypass Control:** Configure how many times a user can skip MFA setup, with the default set to zero.
* **One-Time Password (OTP) Validity:** Define the lifespan of email OTP codes and adjust clock skew tolerance to accommodate potential time discrepancies when validating codes, reducing login issues.
* **Remember Browser Feature:** Allow users to mark browsers or devices as trusted, preventing repeated MFA prompts within a configurable validity period (default 8 hours). This feature uses browser fingerprints, which may require re-authentication if device parameters change.
* **Browser Trust Limits:** Set the maximum number of browsers remembered per user and control default behavior of the "remember this browser" option during MFA validation.
* **Passwordless Authentication Support:** Enable FIDO2-based methods like hardware keys and biometric authentication for MFA.
* **Email OTP Factor:** Optionally enable email-based one-time passwords as an MFA factor.
* **User Interface Enhancements:** Enable MFA factors for users who have not set up an authenticator app, improving flexibility in MFA adoption.
## Practical Use for ServiceNow Customers
By configuring these system properties, you can tailor MFA enforcement to your organization's security policies, providing a balance between strong authentication and user convenience. The ability to remember trusted browsers reduces friction for frequent users, while options for passwordless and email OTP methods expand MFA accessibility. Adjusting OTP validity and clock skew helps prevent login failures due to timing issues. Overall, these settings enable you to implement robust and user-friendly MFA across your ServiceNow instance.
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/OTXBG2s1yKF9qdmO_wxJZg "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 60. The default is 10. 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}