.png?sv=2022-11-02&spr=https&st=2025-02-05T19%3A05%3A43Z&se=2025-02-05T19%3A15%3A43Z&sr=c&sp=r&sig=TI%2FxlEYcQNJC5ZmHH6W%2FI%2F7RkRSqh2nuLYfJxT%2BGSN8%3D){kind=logo}
Required Users Accounts in Dependencies
- 24 Jan 2025
-
DarkLight
-
PDF
Required Users Accounts in Dependencies
- Updated on 24 Jan 2025
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
The validated designs are very opinionated installations of Itential and its dependencies.
The following user accounts are required by the dependencies for a validated design and are used for the following purposes.
MongoDB
| Account | Description |
|---|---|
admin |
Has full root access to the mongo database. Can read and write to any logical database. Can be used to issue admin commands like forcing an election and configuring replica sets. This is NOT used by the Itential application but is created for admin purposes. |
itential |
Has read and write access to the “itential” database only. This is the account used by the Itential Platform application. |
localaaa |
Has read and write access to the “LocalAAA” database. This is used by the Local AAA adapter for local, non-LDAP logins. |
Redis
| Account | Description |
|---|---|
admin |
Has full root access to the Redis database, all channels, all keys, all commands. This is NOT used by the Itential application but is created for admin purposes. |
itential |
Has full access to the Redis database, all channels, all keys, EXCEPT the following commands: asking, cluster, readonly, readwrite, bgrewriteaof, bgsave, failover, flushall, flushdb, psync, replconf, replicaof, save, shutdown, sync. This is the account used by the Itential Platform application. |
Was this article helpful?
