> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/help-and-support/support-articles/kb000003.md).

# KB000003: Configuring the Access Manager Agent to manage an account other than 'root' on Linux

## Summary

{% hint style="info" %}
Content on this pages applies only to agents running v2. Agents running v3 have native support for changing the account name in the policy configured on the AMS server
{% endhint %}

The Access Manager Agent for Linux is configured by default to manage the password of an account named `root`. You can configure the agent to manage an account with a different name.

## Resolution

Modify the `/etc/LithnetAccessManagerAgent.conf` file to include the `Unix` and `Username` fields as shown below, replacing `adminuser` with your desired username. Be sure to match the braces, and provide the comma before the `Unix` element.

```json
{
  "Logging": {
    "LogLevel": {
      "Default": "Trace",
      "Microsoft": "Warning",
      "System.Net": "Warning",
      "Microsoft.Hosting.Lifetime": "Information"
    }
  },
  "Unix": {
    "Username": "adminuser"
  }
}
```

## Notes

The name of the account whose password is being managed is only visible to users in the web app when using Enterprise edition. Community edition users will be able to access the password, but the username will not be shown.


---

# 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.lithnet.io/ams/help-and-support/support-articles/kb000003.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.