User
This entity represents a user who has logged into XDM and used the product. It stores various information about the user, such as their name and group membership.
A user is automatically created upon login, and the data is synchronized with the underlying authentication provider, such as LDAP or any other OpenID provider.
Properties
The table below documents the available properties for users. The 'name' column displays the property name as it can be used in Groovy and Java Scripts.
Name |
Type |
Default |
Description |
|---|---|---|---|
|
active |
Boolean |
true |
This flag indicates whether the user is active or inactive. Inactive users are typically disabled by an administrator and are not allowed to log into the XDM user interface. |
|
admin |
Boolean |
n/a |
This flag indicates whether the user is in one of the defined administration roles and has administration permissions. |
|
authorities |
String |
n/a |
The list of roles in which the user is a member of. These roles are provided by the used authorization provide like LDAP, OpenID. |
|
|
String |
n/a |
This field stores the user’s email address. The email address is only available if the underlying authentication provider, such as LDAP or OpenID, makes the email address available to XDM during the login process. |
|
lastLogin |
Timestamp |
n/a |
A timestamp of the user’s last login. |
|
name |
String |
n/a |
This field stores the full name of the user. It contains the first and last name of the user. It is only available if the underlying authentication provider, such as LDAP or OpenID, makes the full name available to XDM during the login process. |
|
purchaser |
Boolean |
n/a |
This flag indicates if the user is a member of the purchaser role. |
|
userName |
String |
n/a |
The technical user ID of the current user. This is the user ID used to log in at the XDM user interface. |
Actions
The available actions are described below. Some actions apply to the list, while others are specific to selected users.
Object Actions
The following actions are available on specific users. In order to execute the action, the user must possess the necessary permissions for the object. The permissions required for each action are described individually. If the user does not have these permissions, the action will be disabled and the tooltip will provide the exact reason for the deactivation.
-
Edit
Opens the current entity in edit mode.
The following permissions are required:
-
Global admin