Overview
The RuntimeUsers allows to extend the Users with authorization to access the Solution when it is running, dynamically extending the list of the solution's users.
On this page:
Understanding RuntimeUsers
The combination of the Runtime Users and the ones defined at the SecurityUsers table are called Solution Users.
The main difference between the two is that engineering users can access the software's engineering mode, allowing them to design and configure the project. In contrast, runtime users only can use the application, they cannot change the project configuration or design since they don't have access to the engineering mode.
Another distinction is that the regular Users are defined within the Solution file itself, as the Runtime Users are defined in external Security Servers or databases.
The RuntimeUsers can be enabled from the following sources:
- Creating RuntimeUsers with Scripts, using the Security namespace
- From External SQL databases (As defined in the Dataset.DB.RuntimeUsers connections)
- Integration with AD or LDAP server
RuntimeUsers SQL Table
At Security / RuntimeUsers, you can access the contents of the RuntimeUsers defined on the external SQL database.
That database is defined by the configuration of the object Dataset.DB.RuntimeUsers.
When the solution is created, by default that table is created using a SQLite database.
This table is Read-Only for the Designer, to modify the list of Users, you must modify the source Database directly, or use the Script CreateUser methods.
Property | Description (Read-only) |
|---|---|
ID | Displays the unique identifier of the runtime user as defined in the system. |
Name | Displays the name of the runtime user as registered in the system. |
LockState | Displays the current lock state of the runtime user's account according to the system's security protocols. |
Permissions | Displays the list of permissions granted to the runtime user, as specified in the security permissions table. |
Password | Displays the runtime user's password in a secure, encrypted format. |
PasswordHint | Displays the hint associated with the runtime user's password, as set during account creation or update. |
Policy | Displays the security policy applied to the runtime user, as defined in the security policies table. |
Blocked | Displays whether the runtime user is currently blocked from accessing the system, based on security settings. |
Deleted | Displays if the runtime user's account has been marked for deletion in the system. |
DateModified | Displays the date and time when the runtime user's details were last modified in the system. |
DateCreated | Displays the date and time when the runtime user's account was created in the system. |
ContactInfo | Displays the runtime user's contact information as recorded in the system. |
Level | Displays the runtime user's level or rank, as designated in the user management system. |
Category | Displays the category of the runtime user, reflecting their role or type as defined in the system. |
Alias | Displays an alternate name or identifier for the runtime user, as set in the system. |
Company | Displays the company or organization linked to the runtime user, as recorded in the system. |
UserGroup | Displays the group or department to which the runtime user is assigned, as specified in the system. |
InvalidAttempts | Displays the count of invalid login attempts by the runtime user, as tracked by the system. |
LastChangePasswordUTC_Ticks | Displays the timestamp in UTC ticks of the last password change by the runtime user, as logged by the system. |
ChangePasswordRequired | Displays whether the runtime user is required to change their password at the next login, as per system policy. |
LastBlockedUserUTC_Ticks | Displays the timestamp in UTC ticks when the runtime user was last blocked, as logged in the system. |
RuntimeUsers from AD or LDAP
RuntimeUsers who access the Solution based on AD/LDAP validation will not appear in the RuntimeUsers Database. These users are created directly in memory while the Solution is running, as their usernames and permissions are managed by external security servers
For Information to use AD/LDAP go to Windows AD / LDAP Server.
In this section: