---
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


---

# Account recovery (ACR)

# Account recovery (ACR) {#ariaid-title1}

Release version: Brazil  
Updated September 10, 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 Account recovery (ACR)

Account Recovery (ACR) in ServiceNow allows administrators to bypass Single Sign-On (SSO) login issues, such as misconfigurations or expired certificates, by using designated account recovery users.
This feature is essential for maintaining administrative access when SSO is enabled, providing a secure self-service recovery option while reducing unauthorized access risks.
Show full answer Show less  
Enabling ACR disables local username and password logins once SSO is activated, ensuring secure recovery workflows outside of SSO.

## Key Features

* Bypass SSO login to address configuration or certificate issues via account recovery users.
* Self-service recovery flows enable administrators to regain access without disabling SSO.
* Strong security foundation by reducing unauthorized access and enforcing MFA for recovery users.
* Integration with Multi-SSO plugin (com.snc.integration.sso.multi.installer) ensures compatibility with multiple SSO providers.

## Setup and Configuration

### Fresh Instances

* Activate the Multi-SSO plugin.
* ACR is enabled by default; administrators must enroll as ACR users before enabling SSO.
* Administrators must set a local login password and register Multi-Factor Authentication (MFA) before enrollment.
* Disabling ACR requires also disabling the related system property (glide.sso.acr.enabled) to allow local login.

### Upgraded Instances

* Activate the Multi-SSO plugin and explicitly enable ACR.
* Administrators must enroll as ACR users, set local passwords, and register MFA before enabling SSO.
* SSO continues to function without recovery users if upgrading to Rome or later but configuring recovery users is recommended.

### Account Recovery User Configuration

* At least one administrator must be registered as an account recovery user before activating SSO.
* This setup ensures there is always a secure fallback for administrative access.

## Account Recovery Policy and Security

Once an account recovery user is registered and SSO is enabled, local login is restricted via the **SSO - ACR Context** authentication policy context. This policy enforces the use of account recovery users for local access, enhancing security and compliance.

Administrators can manage ACR settings and system properties through the Account Recovery Properties page and related configurations.  
Administrators can configure account recovery (ACR) to perform recovery activities such
as addressing SSO misconfiguration or expired certificates.  
Note:  
Enabling ACR disables the local interactive log-ins (username or password based) when SSO is enabled to your instances.

ACR provides the following capabilities:

* Bypass your single sign-on (SSO) login to address issues with SSO configuration as an administrator.
* Log in with using SSO to perform tasks with an administrator account configured as an account recovery.
* ACR flows enable the administrators to use self-service capabilities to address account recovery when there's a need for recovery, for example, SSO miss-configuration, expired certificates.
* Reduce unauthorized access to the instance and provide a strong foundation to use ACR outside SSO use cases.

{#sso-acct-recovery__ul_h42_vwq_jrb}

## Fresh Instance {#sso-acct-recovery__section_hmk_tv5_prb}

For a fresh instance to use ACR, you must do the following:

* Activate Multi-SSO plugin (<kbd class="ph userinput">com.snc.integration.sso.multi.installer</kbd>)
* Enable ACR (<kbd class="ph userinput">glide.sso.acr.enabled</kbd>) - This is enabled by default in case of a fresh instance.
* Before enabling SSO property (<kbd class="ph userinput">glide.authenticate.multisso.enabled</kbd>), the administrator must enroll as an ACR user.  
  Note:  
  Setting this property to false will not disable multi-provider SSO if Account Recovery (ACR) is also enabled on the instance. To log in with a username and password ACR must also be disabled using the glide.sso.acr.enabled property. For details on this property see [Account recovery properties](https://www.servicenow.com/docs/HKmbcN8VvLObQSu77EIdCA "Use system properties to configure Account Recovery (ACR) on your instance.").
* Administrator must set a password for local login and register MFA before enrolling as an ACR user.
{#sso-acct-recovery__ul_hkw_wxq_jrb}

## Upgraded Instance {#sso-acct-recovery__section_gmz_5v5_prb}

For an upgraded instance to use ACR, you must do the following:

* Activate Multi-SSO plugin (<kbd class="ph userinput">com.snc.integration.sso.multi.installer</kbd>)
* Enable ACR (<kbd class="ph userinput">glide.sso.acr.enabled</kbd>)  
  Note:  
  In case of upgraded instance, the administrator must enable ACR.
* Before enabling SSO property (<kbd class="ph userinput">glide.authenticate.multisso.enabled</kbd>), the administrator must enroll as an ACR user.
* Administrator must set a password for local login and register MFA before enrolling as an ACR user.
{#sso-acct-recovery__ul_vkq_t22_krb}

## Configure account recovery users {#sso-acct-recovery__section_zwg_dcc_gqb}

To use account recovery, you must register at least one admin account as an account recovery user. Single sign-on can't be activated on your instance until there is at least one account configured. For details on this process, see [Configure an account recovery user from the Account Recovery Properties page](https://www.servicenow.com/docs/7e9JO7EaLobD_cQVYEWrCw#config-acct-recovery "Configure an account recovery from the Account Recovery properties page.").  
Note:  
If you're upgrading an instance already using single sign-on to Rome or a later release, single-sign on will continue to function without a recovery user configured.

## Account recovery configuration {#sso-acct-recovery__section_xz5_b2c_gqb}

The account recovery feature is included with the Integration - Multiple Provider Single Sign-On Installer (com.snc.integration.sso.multi.installer) plugins. The
feature is enabled by default. You can change this and other account recovery settings using
system properties. For details on these properties, see [Account recovery properties](https://www.servicenow.com/docs/HKmbcN8VvLObQSu77EIdCA "Use system properties to configure Account Recovery (ACR) on your instance.").

## Account recovery policy context {#sso-acct-recovery__section_cyh_sfc_gqb}

After you've registered an account recovery user and enabled single sign-on (SSO), your
instance restricts all local logins. This restriction is defined in the SSO - ACR Context auth policy context. For more information about the context, see [Account recovery context](https://www.servicenow.com/docs/XJXEfPbe6viY61MtrjcRwQ "The account recovery context uses a policy to define how and when the account recovery can be established.").

For details on how authentication policies and policy contexts, and how they work on your
instance, see [Adaptive authentication](https://www.servicenow.com/docs/CZ1~TzEChB9sygj2Nrp~gg "Use the Adaptive authentication policy framework to enforce contextual authentication controls to the right users at the right time. Adaptive authentication uses authentication policies to evaluate authentication requests and then either deny or allow access to your instance based on the specified policy conditions.").

