Add a website

A Website in strongDM is the combination of an IP/DNS address and authentication information used to connect to a Web-based resource, such as a Redash or Grafana dashboard.

Currently, strongDM supports websites with no authentication, basic HTTP authentication, or header-based authentication. Interactive logins and websites secured with SSO are not supported.

Resource configuration

  1. Display Name: Required. Like other resource types, this is the name that is displayed in the CLI and GUI for any users that are granted access.
  2. Server Type: Required. HTTP, HTTP Basic Auth, HTTP Custom Auth. Find a description for each in the next section.
  3. Base URL: Required. A base address and port for the website you wish to add as a resource. (e.g.
  4. HTTP Subdomain: Required. Be sure to input URL safe characters; this string will be used as your local DNS address. (e.g. app-prod1 would turn into The subdomain entered must be unique.
  5. Default Path: Optional. This path will be the starting page when accessing the resource. (e.g. /_plugins/kibana)
  6. Healthcheck Path: Optional. Change the healthcheck from the default / to a more specific URL; the path provided should return a healthy status code. (e.g. 200)
  7. Headers exclusion: Optional. By default, the logs in strongDM will include all of the headers passed to the Website. If you wish to exclude any headers from logging, you may enter them here.

Server Types

  1. HTTP. This type of connection does not attempt to perform any authentication via strongDM, so it has no additional fields required. Just make sure your URL is correct and go from there!
  2. HTTP Basic Auth. This option uses standard HTTP authentication (username/password). Choosing this option will expose two additional fields: the username (Digest Auth User) and password (Digest Auth Password).
  3. HTTP Custom Auth. This option sends custom authentication data using the Authentication header. Once selected the field Authorization Header will be exposed.

Proxy configuration

Once a user has access to a Website, they will also need to configure their local system proxy. Users can add the following PAC file to their system to accomplish this:

The PAC file in the link above will automatically configure your system to proxy traffic for your Websites. For more detailed setup instructions read: Connecting to Websites

If any errors occur, please copy them into an email and send to

User Impersonation Mode for Kubernetes