> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/troubleshooting/signing-in/unlocksysadmin.md).

# Unlock sysadmin

Clearing the account-locked flags on the sysadmin account directly in the database, when the password is known but the account is locked out.

| Symptom                                                                                | Likely cause                                                                                      | Resolution                             |
| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | -------------------------------------- |
| `sysadmin` cannot sign in on a new installation, and the password is known to be right | The account locked itself after failed attempts, and there is no other administrator to unlock it | Clear the flags in the database, below |

This is the bootstrap case: `sysadmin` is the only account, so there is nobody to unlock it from the Webconsole. **It only applies when you know the password** — it clears the lock, not the credential.

{% hint style="info" %}
`sysadmin` is seeded as `USER_ID` **3000**, which is what the statements below key on.
{% endhint %}

## Reach the database

Connect to the `openiam` schema with the deployment's own database client and credentials. The database username is in the secret store as `vault.secret.jdbc.username` — see [Reading a credential from the secret store](/installation/commands.md).

## Clear the lock

{% code overflow="wrap" %}

```sql
update USERS set SECONDARY_STATUS=null where USER_ID='3000';
update LOGIN set LOCK_MARKER='NOT_LOCKED', AUTH_FAIL_COUNT='0', CHALLENGE_RESPONSE_FAIL_COUNT='0' where USER_ID='3000';
commit;
```

{% endcode %}

## Restart OpenIAM

```bash
openiam-cli stop
openiam-cli start
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/troubleshooting/signing-in/unlocksysadmin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.