Getting Started


This guide provides the User with the information needed to run DKube after installation.

  • An access URL, and all of the necessary credentials for the application, will be provided
  • If you are the DKube Operator, a license token will be provided
  • After installation, the system is initially set up for local use. A single user is enabled.
  • Example models & datasets for DKube are available as part of the installation
  • An initial guide to getting started with the platform is provided at Using DKube
  • A tutorial is available to step you through your first use in section Data Scientist Tutorial

Initiating Dashboard and Workflow Screens

  • Access the DKube site at the URL provided
    • Chrome and Firefox browsers are supported
  • If the DKube instance has not yet been signed in, sign in with the credentials provided. The login will be either local or through a backend authorization, as described below.


If you get a message that your connection is not private, it is because the certificate is self-signed. Please proceed to the url.


If you get an “Authentication Failed” or “Network Error” message after reaching the login page, simply refresh your browser window. This is not a valid error.

  • If the login flow asks for the account to be authorized, please select the authorize button and provide the credentials.
  • This will bring up the DKube dashboard. For subsequent launches, the credentials will be remembered, and the login screen will not appear. DKube periodically forces a new login.

Providing the License Token

If the system is being used for the first time, or if the previous license has expired, a license token needs to be entered in order to use the system. If you are an Operator, you will be provided with a token to use when this happens. Paste in the token provided and select submit.


The same process is used to renew the license when it expires. The Operator can update the license at any time as described at DKube License Update.

Authentication Credentials

There are several authorization mechanisms for accessing DKube.

Local Authorization

Local authorization is used to access DKube after installation. It is based on a username and password. The credentials were provided as part of the installation process, and you will receive them from the cluster manager.

Local authorization allows the user to operate as both an Operator and Data Scientist (see below Using DKube). Most of the functions of DKube are active when locally authorized, and it is meant to allow the product to be tested, or to allow one organization to install DKube and then hand it over to another organization.

In order to allow other users to be added to the system, and before doing significant work, a backend authorization should be activated. Once the backend authorization is activated, DKube cannot go back to local authorization.


After activating the backend credentials, the work performed as part of the local authorization is lost.

Backend Authorization

A backend authorization allows Users to be added to Groups and share Pools, as described in the section Using DKube. All of the functions of DKube are available in this mode. In order to move from local to backend authorization, the Operator selects the OAuth menu item on the left.

This will bring up the “OAuth Providers” screen.


The “Activate” button should be selected under the “Actions” column, and this will bring up the appropriate authorization popup screen.

GitHub Authorization


The GitHub credentials are as follows:

Git User Name GitHub user name for operator
Organization Name GitHub organization name
Client ID GitHub Client ID from OAuth app (see Create OAuth App)
Client Secret GitHub Client Secret from OAuth app (see Create OAuth App)
Access Token GitHub access token (see Create GitHub Token)
OAuth Details

For the OAuth App, the following field definitions are required. The “access url” is the url that is used to run DKube from your browser.

Homepage URL https://<Access url>:32222
Authorization callback URL https://<Access url>:32222/callback


Note that the access url needs be “https://

Access Token Details

During the creation of the GitHub access token, the “repo” permissions should be selected.



The GitHub access token should be saved for future use. It cannot be viewed after the initial token creation is completed.

LDAP Authorization