--- sourceDocument: Yokohama Platform security sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/platform-security Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Platform security ft:clusterId : - psec bundleId : - psec workflow : - Platform --- # MFA enforcement timeline # MFA enforcement timeline {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](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 MFA enforcement timeline The MFA enforcement timeline outlines how and when multi-factor authentication (MFA) becomes mandatory for internal users in ServiceNow instances running Yokohama or later releases. It ensures that users adopt MFA within a defined self-enrollment period, enhancing account security especially for those using local or LDAP authentication. Show full answer Show less ## Enforcement and Self-Enrollment Period * Eligible internal users (without the `sncexternal` role) must complete MFA setup within a 30-day self-enrollment period after their first successful login using local or LDAP authentication. This period is controlled by the `glide.authenticate.multifactor.selfenrolmentperiod` system property, which defaults to 30 days and can be adjusted up to a maximum of 90 days. * After 90 days from upgrading to Yokohama or later, any internal user logging in for the first time with local or LDAP authentication is required to use MFA immediately without a self-enrollment window. This enforcement timing is managed by the `glide.authenticate.multifactor.enforcement.maxrelaxationperiod` property, which can be set up to 270 days. ## Adjusting MFA Enforcement Timelines * Administrators can customize the self-enrollment window by modifying `glide.authenticate.multifactor.selfenrolmentperiod`. Setting this value to 0 enforces immediate MFA setup after the first login. * The period during which users have the self-enrollment window post-upgrade is controlled by `glide.authenticate.multifactor.enforcement.maxrelaxationperiod`. ## User and Administrator Notifications * Users authenticating via local or LDAP methods will see informational messages about MFA enrollment on login and on their profile page. This notification does not appear for users logging in via SSO. * Administrators receive a distinct information message upon login regardless of authentication method, which persists until acknowledged by setting `glide.authenticate.multifactor.enforcement.acknowledged` to true. * To disable user notifications, admins can set `glide.authenticate.multifactor.enforcement.showuserinfomessage` to false. * Admin messages cease after acknowledgment via the aforementioned property. ## Compatibility with Existing MFA Policies If your instance already has an active Adaptive Authentication MFA context policy configured, the new default secure MFA enforcement policy will not override it. However, if MFA was enabled via the property `glide.authenticate.multifactor` but no active MFA policy exists, the default secure MFA policy enforcing MFA for internal users with local or LDAP authentication will apply. FAQ related to MFA enforcement timelines and why it's important. 1. When is MFA enforced?According to the MFA policy, eligible users who haven't completed the MFA setup has a 30-day self-enrollment period. The behavior is controlled using the system property `glide.authenticate.multifactor.self_enrolment_period`. The property's default value is 30 days. It can be updated to a maximum of 90 days. All internal users (users who don't have a `snc_external` role) logging in with local or LDAP authentication must set up MFA within 30 days of their first successful login. During this time, you can log in normally but see a message at the time of login to enroll in MFA. After 90 days of upgrading to Yokohama or a later release, if an internal user (user without the `snc_external` role) logs in with local or LDAP authentication for the first time, they'll be required to use MFA immediately. You don't have the 30-day MFA self-enrollment window. This period is governed by a system property:` glide.authenticate.multifactor.enforcement.max_relaxation_period`. The maximum value for this property is 270 days. 2. How can the MFA enforcement timeline adjusted? * By updating the value of the property `glide.authenticate.multifactor.self_enrolment_period`, admins can provide a smaller or larger self-enrollment window. Set the property value to 0. The users are required to complete the MFA setup after their first login attempt with local or LDAP login after upgrading to Yokohama or a later release. The maximum duration of the self-enrollment window can be 90 days. Property value set higher than 90 will be treated as 90. * By updating the value of the property `glide.authenticate.multifactor.enforcement.max_relaxation_period` admin can decide how many days post upgrade to the Yokohama or a later release you get the MFA self-enrollment window. {#faq-mfa-enforcement-timeline__ul_kpy_y1j_jdc} 3. How are end users informed about this upcoming change?End users performing local or LDAP authentication who will be enforced with MFA will see an information message after logging in. The same message is available when users visit their profile. {#faq-mfa-enforcement-timeline__table_ypx_dwf_b2c__entry__2} | On the User Profile | On Employee Service Center | |-|-| | | | [Table 1. Enforcement Message] {#faq-mfa-enforcement-timeline__table_ypx_dwf_b2c} This message won't appear for non-admin users performing SSO logins. The admin role will see a different information message after a successful login irrespective of the authentication method used for logging in. This message continues to be displayed until one of the admins acknowledges the update by setting the `glide.authenticate.multifactor.enforcement.acknowledged` property value to true. 4. How to turn off the message displayed to end users about completing the MFA setup when they log in?Admins can update the value of the `glide.authenticate.multifactor.enforcement.show_user_info_message` system property to false to turn off the MFA enrollment information message shown to end users after login. 5. How to turn off the message displayed to administrators about the MFA enforcement?The information message regarding MFA enforcement shown to admin users after login, stops appearing when one of the admins acknowledges it by updating the value of the `glide.authenticate.multifactor.enforcement.acknowledged` system property to true. 6. There's already an MFA policy defined using adaptive authentication based on the security needs of my organization in the instance. Is the policy impacted by the mandate?No, if the instance already has an active Adaptive authentication---MFA context policy, the new default secure MFA policy isn't enforced. If the instance had MFA property enabled (`glide.authenticate.multifactor`) but the MFA policy wasn't active, then the default secure MFA policy for enforcing MFA for all internal users (users who don't have `snc_external` role) performing user name and password-based local or LDAP login is enabled. {#faq-mfa-enforcement-timeline__ol_pfr_zfz_3dc}