Skip to main content

Users

Users are individuals who have access to the UDMG Admin UI and the UDMG REST API and are responsible for configuring, managing, and monitoring UDMG Server and its file transfer operations.

warning

Users must not be confused with Accounts. Users manage UDMG administration and system operations. Accounts represent the entities and configurations that allow your partners (such as customers, vendors, organizations, or automated systems) to exchange files with you.

Before You Begin

Domain Scope

Users are created within a single Domain and can access only Configuration Items in that Domain. Users cannot be shared across Domains. To administer multiple Domains, create a separate User in each Domain.

Role

A User's Role defines what they can view and manage in UDMG. Each User must be assigned exactly one predefined Role; custom roles are not available.

For a description of each Role and its permissions, see the Roles page.

Login Methods

UDMG supports three Login Methods (authentication methods), providing flexibility and scalability options to best meet your needs and security requirements. This versatile authentication framework eliminates the need to choose between security and convenience—organizations can leverage existing LDAP infrastructure, implement modern Single Sign-On (SSO) solutions, or maintain standard authentication, all within a single platform.

MethodDescriptionConfiguration
Standard AuthenticationUDMG uses a manually set username and password stored locally in UDMG.Create Users following the Adding a User steps.
LDAP AuthenticationUDMG authenticates Users against an external LDAP directory and automatically creates Users from directory entries.Configure the LDAP provider following the steps described in the LDAP Configuration section.
SSO AuthenticationUDMG authenticates Users through an external Identity Provider (IdP) and automatically provisions Users.Configure the SSO provider/IdP following the steps described in the Single Sign-On Configuration section.

Concurrent Logins

By default, UDMG restricts each User to a single active session. When a User logs in from a new device or location, any previous session is automatically terminated.

To allow multiple simultaneous sessions per User, set the api.allow_concurrent_user_login argument to true in the Configuration File and restart UDMG Server by running the following command on the Server host:

sudo systemctl restart udmg-server
info

Disabling concurrent logins strengthens security by ensuring that each User can only maintain one active session. However, it may also interrupt legitimate use cases where Users need to stay logged in on multiple devices at the same time.

Two-Factor Authentication

In addition, Admins can require Two-Factor Authentication (2FA) for Users who log in with Standard or LDAP Login Methods. When enabled, Users must enroll in an external authenticator app and provide a time-based one-time code (TOTP) in addition to their primary credentials at each login.

See the 2FA page for management and reset information.

Adding a User

Users can be added in different ways depending on their Login Method:

  • Standard Authentication: Admins create the User manually from the Users page.
  • LDAP Authentication: Users are created automatically according to the LDAP Sync configuration.
  • SSO Authentication: Users are created automatically the first time they authenticate through a configured SSO provider (Just-in-Time provisioning).

To add a User with Standard Authentication, follow these steps:

  1. From the Sidebar, click General > Users.
  2. Click the Add User button above the Users table.
  3. Fill out the fields for the new User using the Field Descriptions table as a guide.
  4. Click Add.

Field Descriptions

This table describes the fields that display on the new User form.

NameDescriptionSpecificationsRequired
User ID (Username)User identifier used when logging in.Yes
First NameUser's first name.Must follow the Standard Naming Pattern.Yes
Last NameUser's last name.Must follow the Standard Naming Pattern.Yes
EmailUser's email address.Must be a valid email address.No
Role

The Role for this User.

Options:

  • Domain Administrator
  • System Administrator
  • Operator
  • Pipeline Management
  • Read-only
The System Administrator Role is only available in the Primary Domain.Yes
PasswordUser's password used when logging in.Must follow the global Password Policy.Yes
Confirm PasswordRe-enter the Password.Re-entered password must match the Password field.Yes
Require Two-Factor Authentication (TOTP)A toggle switch to enable 2FA. When enabled, the User must enroll in an authenticator app and enter a one-time code at each sign-in.User's Login Method must be Standard or LDAP.No
info

The Login Method is automatically set based on how the User was created. See User Metadata below for additional details.

Editing a User

Admins can edit Users in their Domain. To edit a User, follow these steps:

  1. From the Sidebar, click General > Users.
  2. Click the Username of the User you want to edit.
  3. Click the Edit button above the User details.
  4. Edit details for the User, using the Field Descriptions above as a guide.
  5. Click Update.
info

Only Users with Standard and LDAP authentication can be edited, and only specific fields remain editable after creation. Users with SSO (SAML/OIDC) authentication cannot be edited. See Authentication page for more information and editable fields.

Managing Users

Viewing User Details

To view the details of a User, follow these steps:

  1. From the Sidebar, click General > Users.
  2. Click the Username of the User you want to view.

User details include all parameters given in the Field Descriptions table above, plus the following read-only metadata:

User Metadata

NameDescription
UUIDUniversally Unique Identifier of this User.
Login Method

The method the User uses to log in and authenticate with the UDMG Admin UI.

Options:

  • Standard
  • LDAP
  • SAML
  • OIDC
TOTP Enrollment Status

Indicates whether the User has completed Two-Factor Authentication (TOTP) enrollment.

Possible values are:

  • Not Enrolled: The User has not yet set up TOTP.
  • Enrolled: The User has successfully enrolled and must provide a TOTP code at each login.
VersionVersion number of the latest configuration of the User.
CreatedDate and time this User was created.
UpdatedDate and time this User was last updated.
SourceUser's Login Method source. For example, ldap://mft-dc1.udmg.local:389.

Changing a User's Password

If a User's Login Method is Standard, there are two ways to change their password, depending on the Role of the User performing the change.

  • System Administrators and Domain Administrators can change the password of any User, including themselves, by editing the User.
  • All Users can change their own password via the Change Password button in the User Profile.

User Profile

info

If a User forgets their password, an Admin must reset their password. As a best practice, the User should change their password afterward to something only they know with the Change Password function.

Enabling and Disabling Users

Admins can Enable or Disable Users to control their access to UDMG.

  • Enabled (default): The User can log in to the UDMG Admin UI and access the UDMG REST API.
  • Disabled: The User cannot log in to the UDMG Admin UI or access the UDMG REST API.

To enable or disable a User, follow these steps:

  1. From the Sidebar, click General > Users.
  2. Click the Username of the User you want to enable or disable.
  3. Click the Enable or Disable button above the User details, depending on the current status.

Deleting a User

Admins can delete Users in their Domain. Any User can be deleted except the default System Admin, udmg.sys-admin. To delete a User, follow these steps:

  1. From the Sidebar, click General > Users.
  2. Click the Username of the User you want to delete.
  3. Click the Delete button above the User details.
  4. You will be asked to confirm the deletion. Click Continue.
danger

Deletion cannot be undone. Deleting an LDAP or SSO User should be done with caution. To avoid inconsistencies, refer to the appropriate authentication page for more information.