---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Recover from account lockout

# Recover from account lockout {#ariaid-title1}

* Release version: Australia
* 
* Updated May 19, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Unlock the integration user account and clear the password reset flag after repeated
failed validation attempts trigger the account lockout policy.

## Before you begin

Role required: admin

## About this task

Repeated failed connection validation attempts can lock the integration user account. Two fields must be cleared to restore access --- `locked_out` and `password_needs_reset`. Clearing only one field is
insufficient; `password_needs_reset` can independently block authentication even when `locked_out` is false.

## Procedure

1. Navigate to ALLSystem DefinitionScripts - Background.
2. Run the following script, replacing `scan_engine_integration` with your integration user's user name if different.  

       var gr = new GlideRecord('sys_user');
       gr.get('user_name', 'scan_engine_integration');
       gr.setValue('locked_out', false);
       gr.setValue('password_needs_reset', false);
       gr.update();

## Result

The integration user account is unlocked and the password reset flag is cleared.

## What to do next

Before retrying validation, resolve the root cause of the failed attempts. See [Validate your instance connection](https://servicenow-prod.fluidtopics.net/HA6MFEOw7zePlehyV0xnCQ "Validate the connection between registered instances to confirm that authentication and My SN Instances configuration are correct before enabling integrations.") for the full validation troubleshooting checklist.

*[\>]: and then