Secure user management

Secure user management is best achieved by integration with your centralized authentication service. Once the integration is complete, create LDAP authenticated named users to facilitate separation of duties, least privileges, and auditing. Disable the out-of-the-box generic ADMIN and SYSADMIN accounts.

Use LDAP for authentication

As described under System Configuration above, enable LDAP authentication to leverage your enterprise authentication service and enable SSL/TLS to secure LDAP connections.

Create named users

Do not create generic functional accounts such as “QA,” “DEV,” or “TEST.” Such accounts will not leave a proper audit trail and violate the separation of duties principle. Instead, create LDAP authenticated named users.

Assign least privileges

Restrict the admin and sysadmin roles to 1-2 trusted named users each. These roles are highly privileged and must be carefully managed. These roles typically map to a DBA and System Administrator respectively.

For subordinate users who need to refresh VDBs, assign “Data Operator” privilege on the VDB and “Reader” privilege on the dSource.

For subordinate users who need to provision new VDBs from dSources, assign “Provisioner” privilege on the dSource and “Provisioner” privilege on the Group to which they will assign the VDB.

Disable ADMIN and SYSADMIN

Once you have established named Delphix Administrators and Systems Administrators, disable the out-of-the-box sysadmin and admin accounts. You can disable accounts through the CLI.

The default domain user created on Delphix Engines is now admin instead of delphix_admin. Engines created before 5.3.1 and upgraded to 5.3.1 or newer retain the old username delphix_admin. To avoid complications, we recommend you create users with an admin role and disable delphix_admin. If your Delphix Engine is a new engine, log in as admin and ssh admin@yourengine.
Last updated
Oct 9, 2026