Git Product home page Git Product logo

kibana-mithril's Introduction

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

Installing

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

./kibana-plugin install 'https://github.com/codingchili/kibana-mithril/releases/download/1.2.2/mithril-windows-x86_64-7.0.0-beta1.zip'

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

Configuration

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.

Defaults

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

File

  • "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.

MongoDB

  • "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.

Ldap

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.

Features

  • 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 https://github.com/codingchili/kibana-mithril
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
./release.sh <kibana-version>
# example:
./release.sh 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.

Dependencies

  • 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

windows: 
  npm install --global --production windows-build-tools
unix:    
  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.

Troubleshooting

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.

Contributing

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

donate

kibana-mithril's People

Contributors

codingchili avatar dependabot[bot] avatar lakeward avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

kibana-mithril's Issues

Error : kbn-authentication-plugin\" was disabled because it expected Kibana version \"0.1.0\", and found \"5.2.2\"."

please see the last line for error... i.e "kbn-authentication-plugin" was disabled because it expected Kibana version "0.1.0", and found "5.2.2"."

why is it saying expected kibana version is 0.1.0?? as your github read me, you seems to be have tested with 5.xxx..

{"type":"log","@timestamp":"2017-04-24T18:05:48Z","tags":["plugins","debug"],"pid":25840,"dir":"/usr/share/kibana/plugins","message":"Scanning /usr/share/kibana/plugins for plugins"}
{"type":"log","@timestamp":"2017-04-24T18:05:48Z","tags":["plugins","debug"],"pid":25840,"dir":"/usr/share/kibana/src/core_plugins","message":"Scanning /usr/share/kibana/src/core_plugins for plugins"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/plugins/kbn-authentication-plugin/index.js","message":"Found plugin at /usr/share/kibana/plugins/kbn-authentication-plugin/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/console/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/console/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/elasticsearch/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/elasticsearch/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/kbn_doc_views/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/kbn_doc_views/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/kbn_vislib_vis_types/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/kbn_vislib_vis_types/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/kibana/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/kibana/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/markdown_vis/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/markdown_vis/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/metric_vis/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/metric_vis/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/spy_modes/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/spy_modes/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/status_page/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/status_page/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/table_vis/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/table_vis/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/tagcloud/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/tagcloud/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["plugins","debug"],"pid":25840,"path":"/usr/share/kibana/src/core_plugins/timelion/index.js","message":"Found plugin at /usr/share/kibana/src/core_plugins/timelion/index.js"}
{"type":"log","@timestamp":"2017-04-24T18:05:49Z","tags":["warning"],"pid":25840,"message":"Plugin "kbn-authentication-plugin" was disabled because it expected Kibana version "0.1.0", and found "5.2.2"."}

Permission Control for part of menu

@codingchili Thanks for provide useful plugin. If I want to everyone could access the discover page, few people could access the dev tools, What I need to change the source code ? for example, when person access discover page, no need to login, once they access dev tools, should be login first.

Thanks
Wayne

core dumped

Hi, i got this error when enter the username "Illegal instruction (core dumped)"

documentation: configuring LDAP

Reported from kibana-mithril.com

Hi Rob,Nice plugin.I could get it working with default user but unable to get it working with LDAP.Any help would be much appreciated with exact steps for LDAP.

JSON.parse error

i got exception in JSON.parse(data) in file.js

server log [11:32:32.263] [fatal] SyntaxError: Unexpected end of JSON input
at JSON.parse ()

after this exception, content of users.json are cleared

page not found - basepath not supported

hello,
i use elasticsearch 5.6.2, kibana 5.6.2.
in install node modules
then in kibana branch tag v5.6.2 i run it with npm start
kibana is now running on https://localhost:5601/jyo


  log   [04:27:35.166] [info][listening] basePath Proxy running at https://localhost:5601/jyo
kibana authentication plugin by codingchili@github init!

after open url http://localhost:5601 - it don't redirect to https://localhost:5601/jyo/login
but to: https://localhost:5601/login

then i manual open https://localhost:5601/jyo/login
and try post query to server that post to https://localhost:5601/login - which not found.

how can i solve this problem?

Request to add TLS to ldap

Hi,

Is there any plan to support ldaps, so connection between kibana and ldap server with encryption.

so make the connection more secure.

AD LDAP Configuration

Excellent looking plugin, however I am running into an error in the configuration. I've got it configured as follows:

{
  "storage": "ldap",
  "two-factor": {
    "enabled": false,
    "length": 6
  },
  "proxy": {
    "enabled": false,
    "port": 7575,
    "remote": "localhost:5601"
  },
  "authentication": {
    "kbnVersion": "6.6.0",
    "cookie": {
      "ttl": 1209600,
      "path": "/",
      "encoding": "none",
      "isSecure": false,
      "isHttpOnly": true,
      "clearInvalid": true,
      "strictHeader": true
    },
    "secret": null
  },
  "file": {
    "filename": "users.json"
  },
  "ldap": {
    "url": "ldap://SERVERIP:389",
    "admin": {
      "dn": "cn=Username,ou=level2,ou=level1,dc=domain,dc=com",
      "password": "UserPassword"
    },
    "search": {
      "scope": "sub",
      "user-dn": "ou=accounts,ou=level2,ou=level1,dc=domain,dc=com",
#      "group-dn": "ou=groups,ou=system"
    }
  },
  "mongodb": {
    "remote": "mongodb://localhost/plugin"
  }
}

I get the following error on Kibana startup:

{"type":"log","@timestamp":"2019-02-21T10:36:49-06:00","tags":["fatal","root"],"pid":404,"message":"SyntaxError: Unexpected token # in JSON at position 873\n    at JSON.parse (<anonymous>)\n    at load (D:/ElasticStack/Apps/Kibana/6.6/plugins/kibana-mithril/src/config.js:17:19)\n    at Object.<anonymous> (D:/ElasticStack/Apps/Kibana/6.6/plugins/kibana-mithril/src/config.js:21:1)\n    at Module._compile (internal/modules/cjs/loader.js:688:30)\n    at loader (D:\\ElasticStack\\Apps\\Kibana\\6.6\\node_modules\\babel-register\\lib\\node.js:144:5)\n    at Object.require.extensions.(anonymous function) [as .js] (D:\\ElasticStack\\Apps\\Kibana\\6.6\\node_modules\\babel-register\\lib\\node.js:154:7)\n    at Module.load (internal/modules/cjs/loader.js:598:32)\n    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)\n    at Function.Module._load (internal/modules/cjs/loader.js:529:3)\n    at Module.require (internal/modules/cjs/loader.js:636:17)\n    at require (internal/modules/cjs/helpers.js:20:18)\n    at Object.<anonymous> (D:/ElasticStack/Apps/Kibana/6.6/plugins/kibana-mithril/src/authentication/auth.js:9:16)\n    at Module._compile (internal/modules/cjs/loader.js:688:30)\n    at loader (D:\\ElasticStack\\Apps\\Kibana\\6.6\\node_modules\\babel-register\\lib\\node.js:144:5)\n    at Object.require.extensions.(anonymous function) [as .js] (D:\\ElasticStack\\Apps\\Kibana\\6.6\\node_modules\\babel-register\\lib\\node.js:154:7)\n    at Module.load (internal/modules/cjs/loader.js:598:32)\n    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)\n    at Function.Module._load (internal/modules/cjs/loader.js:529:3)\n    at Module.require (internal/modules/cjs/loader.js:636:17)\n    at require (internal/modules/cjs/helpers.js:20:18)\n    at Object.<anonymous> (D:/ElasticStack/Apps/Kibana/6.6/plugins/kibana-mithril/src/api/filter.js:12:24)\n    at Module._compile (internal/modules/cjs/loader.js:688:30)\n    at loader (D:\\ElasticStack\\Apps\\Kibana\\6.6\\node_modules\\babel-register\\lib\\node.js:144:5)\n    at Object.require.extensions.(anonymous function) [as .js] (D:\\ElasticStack\\Apps\\Kibana\\6.6\\node_modules\\babel-register\\lib\\node.js:154:7)\n    at Module.load (internal/modules/cjs/loader.js:598:32)\n    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)\n    at Function.Module._load (internal/modules/cjs/loader.js:529:3)\n    at Module.require (internal/modules/cjs/loader.js:636:17)"}

I'm not well versed in the language but it looks like it isn't happy with the path setting in config.json? I have not made any modifications to the users.json file as I'm unsure of what exactly its supposed to contain. I've currently got MFA set to disable as I just want to verify LDAP authentication is up and running.

Release version 1.0

Release tasks

  • finish all jiras for v1.0 milestone
  • update the readme to include new configuration
  • make the travis build pass

Question - Current status

Hi, this is a cool project. Just wanted to check on following with you:

  1. Does it work on Kibana 4.x? Is 5.0 a pre-requisite?

  2. What is the current status on auth? Is 2FA is working already?

  3. Which is the stable version where basic authentication functionality is working with single user i.e. no user management is required.

incompatible version

I use kibana 6.7.1.which version do i need install plugin?i have install 6.6.1 and 7.0.It shows incompatible

image

How to Remove Old 2FA Device and Register New One?

Hi,

Was using the mithril plugin integrated with my AD, and was able to set up the environment fine.

Unfortunately, one of the users had to have their phone undergo factory reset, resulting in the old device being no longer valid.

How can I delete the old 2FA device and let the AD user register a new one?

Thanks

Creating users ( Also some documentation?)

Hey,

Trying to use your (awesome) plugin but after a lot of fiddling I cant for the life of me figure out how to create a user. I've tried with the argon lib to manually generate a password. I'm only able to login with the default "username" "password" and all I see on the authentication panel is "default" group.
When I put in a user of my own, the authentication fails.

Scrolling through the code, i can see the file storage has a "create" function. I'm guessing I'm missing something.

Also, does the LDAP mode supports ActiveDirectory?

Tried with 5.4.0 and 5.6.2
Everything runs in docker.

Thanks for your work!

invalid ELF header

Reported from kibana-mithril.com

Hi, I am unable to install this 2FA with version 6.6.0 of Kibana.

Initially using the default kbn-authentication-plugin.zip package, I ran into the error message 6.6.0 is not compatible with 6.3.2. Thus, I changed the version from 6.3.2 to 6.6.0 in the package.json file.

I reran the plugin installation and this time the following error message showed up: FATAL Error: /usr/share/kibana/plugins/kbn-authentication-plugin/node_modules/ref-napi/build/Release/binding.node: invalid ELF header

Please let me know if there is anything I am doing incorrectly and what needs to be corrected for me to make this work. Thank you for your help!

Error: read ECONNRESET

Hi,

Seems to be facing this intermittent issue, where the Kibana service stops every ~20mins.

My team is seeing the below logs when Kibana service faces an error:
image

Upon inspecting closer, it seems like the LDAP session could be closed every few moments, based on this link: ldapjs/node-ldapjs#318 (comment). (it was mentioned that setting a "reconnect: true" option when creating the LDAP client could help address the issue).

Wanted to check if this item can be handled? Not sure if adding the "reconnect: true" option here helps: https://github.com/codingchili/kibana-mithril/blob/master/src/authentication/ldap.js#L62

Thanks.

documentation: building an installable zip

Reported from kibana-mithril.com

Hi Robin,

How can i compile code into zip file so that it can be deployed on he kibana nodes running on production?

I am not able to find any tutorial which explains the process of kibana plugin compilation into zip file.

Your help will be highly appreciated.

Regards
Deepak Kumar

Supports ELK Version : 7.10.0 and 7.10.1

@codingchili

Does kibana mithril support eLK version 7.10.0? ..
Need step by step installation in centos 7.X. For 1 year I have been looking for this kind of tool in my production deployment. Kindly share the installation instruction for ELK ver 7.10.0.

[root@elk-logging bin]# ./kibana-plugin install 'https://github.com/codingchili/kibana-mithril/releases/download/1.2.1/mithril-windows-x86_64-7.0.0-beta1.zip' --allow-root
Found previous install attempt. Deleting...
Attempting to transfer from https://github.com/codingchili/kibana-mithril/releases/download/1.2.1/mithril-windows-x86_64-7.0.0-beta1.zip
Transferring 20609584 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Plugin installation was unsuccessful due to error "No kibana plugins found in archive"

Tried to build
./release.sh 7.10.0

./kibana-plugin install /root/ldap-kibana/kibana/kibana-mithril/build/dist/mithril-GNU.Linux-x86_64-7.10.0.zip --allow-root
Found previous install attempt. Deleting...
Attempting to transfer from /root/ldap-kibana/kibana/kibana-mithril/build/dist/mithril-GNU.Linux-x86_64-7.10.0.zip
Attempting to transfer from https://artifacts.elastic.co/downloads/kibana-plugins//root/ldap-kibana/kibana/kibana-mithril/build/dist/mithril-GNU.Linux-x86_64-7.10.0.zip//root/ldap-kibana/kibana/kibana-mithril/build/dist/mithril-GNU.Linux-x86_64-7.10.0.zip-7.10.0.zip
Plugin installation was unsuccessful due to error "No valid url specified."

[root@elk-logging bin]# ./kibana-plugin install file:///root/ldap-kibana/mithril-GNU.Linux-x86_64-7.0.0-beta1.zip --allow-root
Found previous install attempt. Deleting...
Attempting to transfer from file:///root/ldap-kibana/mithril-GNU.Linux-x86_64-7.0.0-beta1.zip
Transferring 14397620 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Plugin installation was unsuccessful due to error "No kibana plugins found in archive"
[root@elk-logging bin]#

Compatibility with 6.4.2/7.0.0 (from 6.3.2)

Compatibility

  • kibana 7.0.0-alpha1
  • kibana 7.0.0-beta1
  • kibana 6,4,2

Broken features

  • upgrade hapi to v17.
  • make sure plugin init can be async as this is required by hapi.register now.
  • replace kibana.Plugin with new kibana.Plugin in index.js
  • prevent webpack from failing for our .jade files.
  • x-pack /login route conflicts with mithril's /login.
  • no longer able to register authentication strategy as one already exists.
  • the plugin icon is not visible in the menu.
  • the plugin page does not render, just prints the template as plain text.
  • __KBN__ is no longer defined, we used it to get the version.
  • logging out does not work - set cookie to null has no effect. use unstate?
  • cookie is not set when 2FA is activated the first time.

work in progress on branch hapi_upgrade_17.

remove jade - webpack doesn't like it.

and we are forced to rename the template files from .jade to .tmpl. Anyways - we should be able to get the kibana version to the client in some other way. And live with plain HTML.

Cannot Find jsonwebtoken

Hi @codingchili

I'm trying to build on a Centos 6 server. I can run npm install without issue, however, when I try to run mocha, I get the following:

Error: Cannot find module 'jsonwebtoken'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/root/kibana/kbn-authentication-plugin/src/authentication/auth.js:7:13)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/root/kibana/kbn-authentication-plugin/src/api/api.js:11:24)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/root/kibana/kbn-authentication-plugin/test/api/api.js:10:13)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at /usr/lib/node_modules/mocha/lib/mocha.js:231:27
at Array.forEach (native)
at Mocha.loadFiles (/usr/lib/node_modules/mocha/lib/mocha.js:228:14)
at Mocha.run (/usr/lib/node_modules/mocha/lib/mocha.js:514:10)
at Object. (/usr/lib/node_modules/mocha/bin/_mocha:359:16)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:383:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:496:3

It's puzzling because the jsonwebtoken module is present in the node_modules directory.

Any ideas?

Thanks!
James

update pug

3 warnings from npm audit on dependencies of pug.

Compatibility with 6.x version

Hi,

I tried using your plugin on kibana 6.2.2.
I followed all the instructions and after installing the plugin and running kibana, kibana runs normally and the plugin doesn't show.

Looking at kibana console, I think the plugin isn't begin executed even though is installed.

kibana console:
image

plugin list:
image

Have you ever tried to run the plugin in version 6.x or have a fix for the problem?
This plugin fits my needs pretty well and would be amazing to have it working.

Thanks in Advance and keep the amazing work.

kibana-mithril 1.2.1 (6.6.0 or 7.0.0-beta1) will not install on kibana 6.6.1

Probably a trivial thing but the documentation leads me to believe that 1.2.1 will install on kibana 6.6.0 or newer, but it apparently does not:

bash-4.2$ kibana-plugin install 'https://github.com/codingchili/kibana-mithril/releases/download/1.2.1/mithril-GNU.Linux-x86_64-6.6.0.zip'
Found previous install attempt. Deleting...
Attempting to transfer from https://github.com/codingchili/kibana-mithril/releases/download/1.2.1/mithril-GNU.Linux-x86_64-6.6.0.zip
Transferring 14397613 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Extracting plugin archive
Extraction complete
Plugin installation was unsuccessful due to error "Plugin kibana-mithril [6.6.0] is incompatible with Kibana [6.6.1]"
bash-4.2$ kibana-plugin install 'https://github.com/codingchili/kibana-mithril/releases/download/1.2.1/mithril-GNU.Linux-x86_64-7.0.0-beta1.zip'
Attempting to transfer from https://github.com/codingchili/kibana-mithril/releases/download/1.2.1/mithril-GNU.Linux-x86_64-7.0.0-beta1.zip
Transferring 14397620 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Extracting plugin archive
Extraction complete
Plugin installation was unsuccessful due to error "Plugin kibana-mithril [7.0.0] is incompatible with Kibana [6.6.1]"

configuration to enable logging

Logging helps with troubleshooting and auditability.

  • user login
  • user login failure
  • user setup 2FA
  • user fail 2FA
  • some logging framework? can we access kibanas logger?

support for encrypted communications

we'll configure this on the HAPI server. Should be simple to setup - self signed certificates generated on the fly.

  • encrypted communications over TLS
  • support for loading keys from a keystore
  • support for generating a self signed certificate on startup if no keystore set.

Not able to build

Hi, clone the project and trying the build the project. All the dependency are installed.

While building i get the following error.

[email protected] install /home/user/plugins/kbn-authentication-plugin/node_modules/ffi
node-gyp rebuild

make: Entering directory /home/user/plugins/kbn-authentication-plugin/node_modules/ffi/build' CC(target) Release/obj.target/ffi/deps/libffi/src/prep_cif.o ../deps/libffi/src/prep_cif.c:26:17: fatal error: ffi.h: No such file or directory #include <ffi.h> ^ compilation terminated. make: *** [Release/obj.target/ffi/deps/libffi/src/prep_cif.o] Error 1 make: Leaving directory /home/user/plugins/kbn-authentication-plugin/node_modules/ffi/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack at emitTwo (events.js:125:13)
gyp ERR! stack at ChildProcess.emit (events.js:213:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.10.0-514.26.2.el7.x86_64
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/user/plugins/kbn-authentication-plugin/node_modules/ffi
gyp ERR! node -v v8.6.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Let me know if this is a know issue.? Or i am missing something.

Thanks,
Bharath

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.