With the local user manager in Ixolate one can add users and groups and define the privileges for granting access to certain parts of the GUI (Web Configurator).
Adding Users
To add a new user go to System › Access › Users and click on the + sign at the bottom right corner of the form.
| Defined By | information | Shows the source of the user, read only information |
| uid | information | Autogenerated internal user number |
| Disabled | Unchecked | Can be used to (temporarily) disable an account |
| Username | John | A unique username |
| Password | secret | A strong password |
| Scrambled Password | Generate a scrambled password to prevent local database logins for this user. | |
| Full name | John Doe | Optional, Full username, for reference only |
| <a@b.com> | Optional, users email, for reference only | |
| Comment | Optional, comment field, for reference only | |
| Preferred landing page | ui/page | Optional, landing page to visit after login |
| Language | Default | Language to use for this user |
| Login shell | /bin/csh | The shell to use when logging in via the console. |
| Expiration date | Optional, if account should expire enter as mm/dd/yyy | |
| Group Membership | Optional, select one or more groups | |
| Effective Privileges | Optional, additional grants for this user, usually these are being handled via a group | |
| OTP seed | Optional, enter or generate a OTP seed (base32) | |
| Authorized keys | Optional, paste ssh key for ssh console access |
Creating and maintaining API keys
The assigned keys can be found in the “ApiKeys” tab, where you can remove keys that are no longer used.
Creating Groups
Go to System › Access › Groups and click on the + sign in the lower right corner of the form.
Enter a Group name and a Description and add users to the group.
When users should access resources on this firewall via a group, connect the relevant ones via Assigned Privileges.
Validate and change privileges
The System › Access › Privileges privileges page offers quick insights into the roles available and their purpose.
Each component in the same “lives” on it’s own path (endpoint), these are collected into privileges for easy access.
| ID | Internal identifier stored in the database |
| Name | The name of this privilege |
| Match | The different paths this privilege matches on |
| Users | The number of users linked directly into this privilege |
| Groups | The number of groups linked directly into this privilege |