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 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 admin	Boolean	n/a	This flag indicates whether the user is in one of the defined administration roles and has administration permissions.
Authorities 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.
Email email	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.
Last login lastLogin	Timestamp	n/a	A timestamp of the user’s last login.
Name 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 purchaser	Boolean	n/a	This flag indicates if the user is a member of the purchaser role.
User name 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.

Name

Type

Default

Description

Active

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

admin

Boolean

n/a

This flag indicates whether the user is in one of the defined administration roles and has administration permissions.

Authorities

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.

Email

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.

Last login

lastLogin

Timestamp

n/a

A timestamp of the user’s last login.

Name

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

purchaser

Boolean

n/a

This flag indicates if the user is a member of the purchaser role.

User name

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.

List Actions

The following actions are available on the users list. If the action is disabled a tooltip will provide the exact reason for the deactivation. The required permissions are described in detail for each action.

Export

This action allows to export XDM objects in different formats in order to import them via export or CasC in another environment.

Refer to configuration of export for more information.

Related and dependent objects can optionally be included in the export. The export dialog has the following options:

Include dependent objects: Dependent objects only belong to the exported object like rules and tasks.
Include permissions: Permissions of each exported object, only when the object supports permissions. Some objects like rules don’t have permissions.
Include referenced objects: Referenced objects exist by their own and are used in the exported object like connections and environments.
Include objects that depend on referenced objects: Also include the dependent objects of the referenced objects. E.g. the rules of a modification set or the rules in an application model version.
Include implicit created objects: Implicit created objects are tasks or workflows which were automatically created for execution. These objects won’t be exported by default, but can be included by setting this flag. When exporting implicit objects, make sure that the Include dependent objects flag is also enabled.

Objects on which the user does not have READ permission are not exported. This includes dependent and referenced objects. However, the reference to an object will be exported.

For example a connection object would refer to the credential, even if the user does not have READ permission on the credential. The definition of the credential object itself will not be part of the export file. This can lead to issues during the import, because the connection cannot be created without an existing credential.

The following permissions are required on the list:

READ

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