benutzer
| This page was automatically generated from the database schema dump and may be incomplete or incorrect. |
Master-data table of enaio® user accounts. Holds login credentials (user name, password), profile reference, MFA configuration, external-ID mapping and status information.
1. Columns
| Name | Type | Length | Description |
|---|---|---|---|
|
— |
User ID (primary key, internal). Often referenced from other tables as |
|
|
|
— |
Supervisor flag ( |
|
255 |
User name (login ID). Often referenced from other tables as |
|
|
|
255 |
Password (hashed). |
|
|
255 |
Assigned station. |
|
|
— |
Time of the last login as a UNIX timestamp (seconds). |
|
|
— |
Home server of the user ( |
|
|
— |
* The profile configuration (which setting categories are active for the profile user) lives in osprofile — resolved in two steps: first look up the |
|
|
— |
Modified marker. |
|
|
— |
Status flags (bitmask). |
|
|
255 |
Full name (display name). |
|
|
248 |
Free-text remark. |
|
|
— |
Number of successful logins. |
|
|
— |
Lock status of the account (boolean as integer). |
|
|
255 |
Last login station. |
|
32 |
External GUID of the user. Often referenced from other tables as |
|
|
|
248 |
Email address. |
|
|
— |
Type of the user account: * |
|
|
— |
Preferred language of the user. Foreign key to |
|
|
32 |
Start of validity of the user account. Date-time format |
|
|
32 |
End of validity of the user account. Date-time format |
|
|
32 |
GUID of the assigned department. |
|
|
— |
Timestamp of last password change (UNIX time). |
|
|
— |
Flag: password does not expire. |
|
|
— |
Flag: user must change password on next login. |
|
|
— |
MFA activation flag. |
|
|
255 |
MFA secret (TOTP seed or similar). |
|
|
255 |
Login name (may differ from |
|
|
255 |
External ID (for SSO / identity-provider mapping). |
3. References from other tables
The user table is referenced across the entire schema — under varying column names and via three different keys. The following conventions occur frequently:
| Key | Typical column names | Examples |
|---|---|---|
|
|
|
|
|
|
|
|
|
The columns osowner and lockuser appear under both the GUID and the login-name references because they can take on either meaning in different tables or display contexts. The decisive criterion is the column length: nvarchar(32) for GUIDs, nvarchar(255) for login names, int for IDs.
|
4. Usage by Server-API jobs
-
MNG engine (mng) — manages user accounts.
-
krn.SessionLogin — checks credentials against this table.