// Benutzung · Grundlagen
Logging in
- Open the Fleeger admin UI in your browser.
- You will be taken to the Sign in screen.
- Enter your username and password and select Sign in.
- On success you land on the Locations page. Your session is kept until you select Log out (bottom of the left nav) or the session token expires, at which point you are returned to the sign-in screen.
First administrator
Before anyone can log in, an administrator account must exist. There is no self-registration, so an operator creates the first admin from the command line:
auth-svc user add --username <name> --email <email> --role adminYou are prompted for the password (it is not echoed). Additional users can be
created the same way with --role operator or --role viewer, or by an existing
administrator later.
The command is journalled in the audit log as
user.create by cli:<your OS user> (never with the password), written
straight into inventory-svc's audit database before the user is created. It needs that database migrated by inventory-svc db migrate (run by
compose's inventory-migrate one-shot and by the chart's init container), so
run it once the hub is up; before that it refuses and creates nothing.
user delete, user assign-role and migrate-legacy are journalled the
same way.
A username is at most 50 characters and a password at most 128, the longest
sign-in accepts. user add, the Access page and the user API all refuse
longer ones with an error naming the field and the limit.
An account created before that limit with a longer password cannot sign in:
sign-in answers 400 for it rather than 401, even with
the right password. An administrator can give it a new password of at most 128
characters (Access → Password). An account whose name is longer than
50 characters cannot be renamed: delete it and create it again under a shorter
name. Such names can be listed with
SELECT name FROM user WHERE string::len(name) > 50 against db=auth.
What your role lets you do
- viewer / operator — can view Locations and Resources.
- admin — full access, including creating, editing, and deleting Locations and Resources.
If you try an action your role doesn't permit, the UI shows a "missing permission" error and nothing changes.