Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

kibana-mithril Build Status

A plugin that adds authentication to Kibana dashboards! YouTube demo

⚠️⚠️⚠️ This plugin depends on outdated third-party dependencies with known vulnerabilities. ⚠️⚠️⚠️

key setup


To install the plugin use the kibana-plugin utility, example:

./kibana-plugin install ''

Make sure that the kibana version and platform matches.

If there are no releases for your specific version/platform combination please submit a request or build it yourself.

  • Default username and password is: 'username' and 'password' for the file storage.
  • Mithril 1.2.X can coexist with the free version of X-Pack (not gold/plat).
  • Mithril 1.2.X supports using a basePath if rewriteBasePath is set to true. (default in 7.0.0).

To add a new user run the adduser utility, not supported in LDAP mode.

node adduser.js USERNAME PASSWORD


To set where credentials are stored, change 'storage' in config.json. The supported modes are:

  • "mongodb", stores users in a mongodb database.
  • "ldap", stores users in an ldap directory (not supported by adduser utility.)
  • "file", stores users in a .json file on disk.

Two factor authentication can be disabled by setting 'two-factor.enabled' to false.


  • Two factor authentication is enabled.
  • The 'file' storage is used to store users.
  • A secret for securing JWT tokens are generated on startup.


  • "filename", indicates which file user credentials are stored in.

This needs to be configured when using LDAP with two-factor authentication since the secret keys cannot be stored in the LDAP directory.


  • "url", points to a MongoDB server and collection to use.

When using mongoDB as a credentials store, 2FA secrets are also stored in the database.

Note: does not support servers that requires authentication.


In config.js there is some sample configuration for setting up LDAP connectivity.

  • "admin", an user that has privilegies to search for users/groups within the directory.
  • "search", specifies how users are found within the directory.
  • "url", points to an LDAP server that we are connecting to.

Make sure to set the correct version in json.config. The version must match the version of Kibana being used. If you are using file-based authentication, make sure to remove the default user.


  • two factor authentication with time based tokens.
  • supports scanning a barcode in the Google Authenticator app for example.
  • supports storing user credentials and keys in a simple json file.
  • supports storing user credentials and keys in MongoDB.
  • supports storing user credentials in LDAP and keys in a json file.
  • json web token authentication using Kibanas bundled HAPI package.
  • uses the latest password hashing contest winner!
  • logs succeeded and failed login attempts.

Building the plugin

To check out the sources and build the plugin do the following

git clone
cd kibana-mithril
npm install
mocha test --recursive -u tdd

To build an installable zip run the following script

# make sure to match the kibana version
./ <kibana-version>
# example:
./ 6.6.0

This creates an installable zip in build/dist/.

The script can either be executed on a windows machine with gitbash or WSL or on a linux system. jq needs to be installed and available on the path for the script to work.


  • NodeJS 8.11.2+
  • NPM
  • MS Build tools / Unix build tools
  • Python 2.7
  • jq

To compile the binary module argon2-ffi build tools are requried, install with

  npm install --global --production windows-build-tools
  sudo apt-get install build-essential libssl-dev libffi-dev python-dev

This installs MS build tools and python 2.7 and is required for node-gyp to work.


If the Kibana instance is already running it may be set to reload all plugins on change, if not then try restarting the instance.

Kibana compatibility matrix

  • 1.1.0 is compatible with 5.6.4 -> 6.3.2 (requires editing package.json version)
  • 1.2.X is compatible with 6.6.1 and 7.10.1.

If you have issues installing the plugin,

  • make sure that the version in package.json is matching your kibana version.
  • make sure that the native modules are compiled with the same arch as kibanas bundled node.

Known issues

  • Multi-user capabilities is not completed, all authenticated users share the same indice and dashboards.
  • A warning appears on startup stating that the N-API is experimental.
  • Installable zip's needs to be built for each platform windows/linux and each Kibana version.

Maintaining kibana plugins is hard work, the JS world is full of shifting paradigms and backwards compatibility is seldom prioritized. Lack of documentation and quality is a constant nightmare. Due to the heavy cost of upgrading there are few resources for adding new features. The upgrade from Kibana 6.3.2 to 6.4.X came with a truckload of breaking changes and took a week to finish.


Any contributions are welcome, new issues, pull requests, security reviews!