Built-in local authentication

Dash Enterprise uses its own locally managed authentication system by default. When using the default authentication system, user accounts and metadata are stored locally, and, if an SMTP server has also been configured, users are able to reset their own passwords. Dash Enterprise also supports integration with your existing LDAP or SAML authentication server/identity provider.

As of Dash Enterprise 4.0.0, e-mail addresses are supported as usernames when using LDAP or SAML authentication, subject to the following conditions:

  • The address contains no more than one @

  • The @ character must be followed by a domain

  • The domain cannot contain underscores (_)

Dash users should log in using their normal e-mail address as the username. However, when sharing Dash apps with other users, a Dash app owner should replace the @ symbol with an underscore (e.g. if sharing with localpart@domain.com, enter localpart_domain.com).

At this time, Dash Enterprise only supports app deployment over SSH (not HTTPS) when using e-mail addresses as usernames.

Regardless of which authentication mode you are using, you must designate an administrator by checking Create admin user, and:

  • If using local authentication: set the Admin Username and Admin Password fields

    • You may create additional administrators after logging into the Dash user administration panel as this user (see Admin panel reference)

  • If using LDAP or SAML authentication: specify the name of a user that already exists on your authentication server

    • When logging into Dash Enterprise as an administrator, use the password of the designated administrator account as it was set on your LDAP or SAML server

Last updated