Dash Enterprise Administration
4.3.1
4.3.1
  • Changelog
  • Installation
    • Capacity Planning
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • Before you install
    • Dash Enterprise Single Server
      • Installation on cloud provider
      • On-premise installation on own server
      • Fully offline installation
    • Dash Enterprise Kubernetes
      • Amazon Web Services resource prerequisites
      • Google Cloud Platform resource prerequisites
      • Microsoft Azure resource prerequisites
  • Configuration
    • Set up your Server Manager
    • Run preflight checks
    • Configure basic settings
    • Authentication settings
      • Built-in local authentication
      • LDAP authentication
      • SAML authentication
    • Dash Enterprise Kubernetes additional required configuration
    • Configure optional settings
    • Add SELinux permissions to mapped directories
    • Other options and customizations
    • Using Snapshots & Backups
    • Running and logging into Dash Enterprise
    • Next steps
  • Advanced Configuration
    • General troubleshooting and problem solving
      • Dash Enterprise Kubernetes
    • Load balancer configuration
    • Reverse proxy setup instructions
    • Docker storage driver requirements and considerations
    • Import an LDAPS certificate from Active Directory into Dash Enterprise
    • Transfer Dash Enterprise to a new server
    • Sync license changes
    • Change channels for an upgrade
    • Admin panel reference
    • Configure Dash Enterprise to use common SAML IdPs
      • Active Directory Federation Services (AD FS)
      • PingFederate
      • Okta
    • Configure Dash Enterprise to use common LDAP IdPs
      • Okta
  • Upgrade
    • Prepare for the upgrade
    • Upgrade
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • After the upgrade
  • Advanced Troubleshooting
    • Dash Enterprise Architecture and Internals
    • Navigating the System
    • Navigating the Support Bundle
    • Getting Help and Reporting Issues
    • Troubleshooting Specific Issues
Powered by GitBook
On this page

Was this helpful?

  1. Configuration
  2. Authentication settings

Built-in local authentication

PreviousAuthentication settingsNextLDAP authentication

Last updated 2 years ago

Was this helpful?

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 )

  • 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

Admin panel reference