Giter VIP home page Giter VIP logo

elasticsearch-http-user-auth's Introduction

Build Status

Elasticfence - Elasticsearch HTTP Basic User Auth plugin

Elasticsearch user authentication plugin with http basic auth and IP ACL

This plugin provides user authentication APIs and a User management web console.

Installation

bin/plugin install https://raw.githubusercontent.com/elasticfence/elasticsearch-http-user-auth/5.1.2/jar/elasticfence-5.1.2-SNAPSHOT.zip

Build with Maven

mvn package clean
bin/plugin install file:///path/to/repo/jar/elasticfence-5.1.2-SNAPSHOT.zip

Configuration

Enabling/Disabling Elasticfence

elasticfence.disabled: false

To disable the plugin set elasticfence.disabled to true

Root Access

elasticfence.root.password: rootpassword

To set the root password on each start use elasticfence.root.password

Only the root user can access ES's root APIs (like /_cat, /_cluster) and all indices. Other users can access URLs under their own indices that are specified with this plugin's API.

Sharding Scheme

elasticfence.number_of_shards: 1
elasticfence.number_of_replicas: 3

Omit these config options to use the Elasticsearch defaults (currently 5 and 1 respectively), otherwise set them according to desired level of redundancy and cluster scheme.

Basic IP ACL

IPs contained in whitelist array will bypass authentication, blacklisted IPs will be blocked. All other IPs will show an authentication window.

elasticfence.whitelist: ["127.0.0.1", "10.0.0.1"]
elasticfence.blacklist: ["127.0.0.2", "10.0.0.99"]

To block all IPs that are not in the whitelist, use the following option for elasticfence.blacklist

elasticfence.blacklist: ["*"]

Kibana 4

Add index filter "/.kibana" to a your_custom_username which you created on Elasticfence and set it in kibana.yml:

elasticsearch.username: your_custom_username
elasticsearch.password: your_custom_password

Add permissions to your kibana users using regex filters:

/index.*,/_.*,/.kibana,/

Kibana 4.x Auth Plugin

To facilitate users and improve security, the optional Kibana Auth plugin can be deployed alongside Elastifence:

bin/kibana plugin --install kibana-auth-plugin -u https://github.com/elasticfence/kibana-auth-elasticfence/releases/download/snapshot/kauth-latest.tar.gz


Add username and password on HTTP requests

The authentication method of this plugin is Basic Authentication. Therefore, you should add your username and password on URL string. For example:

http://root:[email protected]:9200/
CURL
curl -u root:rootpassword http://your.elasticsearch.hostname:9200/
{
  "status" : 200,
  "name" : "Piranha",
  "cluster_name" : "elastic1",
  "version" : {
    "number" : "1.7.3",
    "build_hash" : "05d4530971ef0ea46d0f4fa6ee64dbc8df659682",
    "build_timestamp" : "2015-10-15T09:14:17Z",
    "build_snapshot" : false,
    "lucene_version" : "4.10.4"
  },
  "tagline" : "You Know, for Search"
}

Plugins using ES's REST API also have to be set root password in their configurations.

The ways of configuring Marvel and Kibana 4 are below:

Marvel

elasticsearch.yml:

marvel.agent.exporter.es.hosts: ["root:[email protected]:9200"]

User Management Console

User Management API

This plugin provides a web API to manage users and permissions.

Add User:
http://your.elasticsearch.hostname:9200/_httpuserauth?mode=adduser&username=admin&password=somepass
Add Index Permissions:
http://your.elasticsearch.hostname:9200/_httpuserauth?mode=addindex&username=admin&index=index*
Update Index Permissions:
http://your.elasticsearch.hostname:9200/_httpuserauth?mode=updateindex&username=admin&index=index-*
Delete User:
http://your.elasticsearch.hostname:9200/_httpuserauth?mode=deleteuser&username=admin
List User(s):
http://your.elasticsearch.hostname:9200/_httpuserauth?mode=list
[{ 
  "username":"admin",
  "password":"7080bfe27990021c562398e79823h920e9a38aa5d3b10c5ff5d8c498305",
  "indices":["/_*"],
  "created":"2015-11-06T21:57:21+0100"
}]

elasticsearch-http-user-auth's People

Contributors

aymandf avatar digitalkaoz avatar kmels avatar lmangani avatar ryanlutgen avatar tommyktech avatar tomsearch 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  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  avatar  avatar  avatar  avatar  avatar

elasticsearch-http-user-auth's Issues

Error in 2.2.1

bin/plugin install https://raw.githubusercontent.com/elasticfence/elasticsearch-http-user-auth/2.2.x/jar/elasticfence-2.2.0-SNAPSHOT.zip

-> Installing from https://raw.githubusercontent.com/elasticfence/elasticsearch-http-user-auth/2.2.x/jar/elasticfence-2.2.0-SNAPSHOT.zip...
Trying https://raw.githubusercontent.com/elasticfence/elasticsearch-http-user-auth/2.2.x/jar/elasticfence-2.2.0-SNAPSHOT.zip ...
Downloading .....................................................DONE
Verifying https://raw.githubusercontent.com/elasticfence/elasticsearch-http-user-auth/2.2.x/jar/elasticfence-2.2.0-SNAPSHOT.zip checksums if available ...
NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Plugin [elasticfence] is incompatible with Elasticsearch [2.2.1]. Was designed for version [2.2.0]

How to fix it ?

Best Wishes !

Failing while creating a new user using elasticsearch-http-user-auth

Hi
I am not able to create a user using this plugin. I want to create a user per index so that index will be accessible only for that particular user.

Elasticsearch v 5.1.2
Elasticsearch-http-user-auth v5.1.2

Added configuration in elasticsearch.yml

elasticfence.disabled: false
elasticfence.root.password: rootpassword

Ran below commands to get the user list

curl -u root:rootpassword http://localhost:9200/_httpuserauth?mode=list
[]

For creating a user ran below commands but i got error

curl -u root:rootpassword http://localhost:9200/_httpuserauth?mode=adduser&username=admin&password=somepass
[1] 28647
[2] 28648
[vagrant@localhost ~]$ User already exists : null

failure

Please help to solve this issue.

Not able to login or add user

Hi,
A newbie question, I have successfully installed the plugin to elasticsearch & Kibana Authentication plugin.
Made the changes in the elasticsearch.yml as per the README.
Added user root with password
Started ES & KIbana
Stuck at the login screen for Kibana.
Which password should i use?

Not able to create new user for elasticsearch using elasticsearch-http-user-auth

Hi
I am not able to create a user using this plugin. I want to create a user per index so that index will be accessible only for that particular user.

Elasticsearch v 5.1.2
Elasticsearch-http-user-auth v5.1.2

Added configuration in elasticsearch.yml

elasticfence.disabled: false
elasticfence.root.password: rootpassword

Ran below commands to get the user list

curl -u root:rootpassword http://localhost:9200/_httpuserauth?mode=list
[]

For creating a user ran below commands but i got error

curl -u root:rootpassword http://localhost:9200/_httpuserauth?mode=adduser&username=admin&password=somepass
[1] 28647
[2] 28648
[vagrant@localhost ~]$ User already exists : null

Please help to solve this issue.

Support of Elasticsearch 2.2 and Kibana 4.4

I'm trying to use the plugin with ES 2.2 and Kibana 4.4

Everything seems to work fine with the exception of Kibana 4.4, I’ve got the following error in the Kibana log when I’m login with a user that I’ve created :

respons [20:28:32.506]  GET /bundles/src/ui/public/images/kibana.svg 304 3ms - 9.0B
respons [20:28:32.508]  GET /bundles/src/ui/public/images/elk.ico 304 5ms - 9.0B
respons [20:28:32.523]  POST /elasticsearch/_mget?timeout=0&ignore_unavailable=true&preference=1455046102682 401 5ms - 9.0B
respons [20:28:32.549]  GET /bundles/src/ui/public/images/elk.ico 200 4ms - 9.0B
respons [20:28:32.549]  GET /bundles/src/ui/public/images/elk.ico 200 3ms - 9.0B
  log   [20:28:32.612] [debug][plugin] Checking Elasticsearch version
  log   [20:28:35.124] [debug][plugin] Checking Elasticsearch version
  ops   [20:28:36.826]  memory: 71.2MB uptime: 0:00:51 load: [0.01 0.02 0.05] delay: 0.389
  log   [20:28:37.647] [debug][plugin] Checking Elasticsearch version
respons [20:28:38.287]  POST /elasticsearch/_mget?timeout=0&ignore_unavailable=true&preference=1455046102682 403 4ms - 9.0B
respons [20:28:38.598]  GET /bundles/node_modules/font-awesome/fonts/fontawesome-webfont.woff2 304 2ms - 9.0B

If I login with the root user it works, see the log of a sucessfull connexion :

respons [20:28:02.520]  POST /elasticsearch/.kibana/config/4.3.1/_update 200 31ms - 9.0B
respons [20:28:03.046]  POST /elasticsearch/_mget?timeout=0&ignore_unavailable=true&preference=1455046060281 200 18ms - 9.0B
respons [20:28:03.089]  POST /elasticsearch/.kibana/index-pattern/netflow-* 200 67ms - 9.0B
  log   [20:28:04.928] [debug][plugin] Checking Elasticsearch version
respons [20:28:05.430]  POST /elasticsearch/.kibana/index-pattern/_search?fields= 200 7ms - 9.0B
respons [20:28:05.783]  POST /elasticsearch/netflow-*/_field_stats?level=indices 200 7ms - 9.0B
respons [20:28:05.870]  POST /elasticsearch/_msearch?timeout=0&ignore_unavailable=true&preference=1455046060281 200 3ms - 9.0B
  ops   [20:28:06.820]  memory: 74.4MB uptime: 0:00:21 load: [0.02 0.02 0.05] delay: 0.487
  log   [20:28:07.461] [debug][plugin] Checking Elasticsearch version
respons [20:28:09.077]  POST /elasticsearch/netflow-*/_field_stats?level=indices 200 5ms - 9.0B
respons [20:28:09.717]  POST /elasticsearch/_msearch?timeout=0&ignore_unavailable=true&preference=1455046060281 200 550ms - 9.0B
  log   [20:28:09.973] [debug][plugin] Checking Elasticsearch version
  ops   [20:28:11.821]  memory: 75.5MB uptime: 0:00:26 load: [0.02 0.02 0.05] delay: 0.464
  log   [20:28:12.487] [debug][plugin] Checking Elasticsearch version
  log   [20:28:15.011] [debug][plugin] Checking Elasticsearch version

My understanding is that Kibana is sending a POST request to /_mget?timeout=0&ignore_unavailable=true&preference=1455046102682 with the following json
{"docs":[{"_index":".kibana","_type":"config","_id":"4.4.0"}]} and I’m assuming that your plugin doesn’t allow this request.

I’ve confirmed with curl that my user has access to the .kibana index :

curl http://dhr:[email protected]:9200/.kibana

{".kibana":{"aliases":{},"mappings":{"dashboard":{"properties":{"description":{"type":"string"},"hits":{"type":"integer"},"kibanaSavedObjectMeta":{"properties":{"searchSourceJSON":{"type":"string"}}},"optionsJSON":{"type":"string"},"panelsJSON":{"type":"string"},"timeFrom":{"type":"string"},"timeRestore":{"type":"boolean"},"timeTo":{"type":"string"},"title":{"type":"string"},"uiStateJSON":{"type":"string"},"version":{"type":"integer"}}},"visualization":{"properties":{"description":{"type":"string"},"kibanaSavedObjectMeta":{"properties":{"searchSourceJSON":{"type":"string"}}},"savedSearchId":{"type":"string"},"title":{"type":"string"},"uiStateJSON":{"type":"string"},"version":{"type":"integer"},"visState":{"type":"string"}}},"index-pattern":{"properties":{"fieldFormatMap":{"type":"string"},"fields":{"type":"string"},"intervalName":{"type":"string"},"timeFieldName":{"type":"string"},"title":{"type":"string"}}},"config":{"properties":{"buildNum":{"type":"string","index":"not_analyzed"},"defaultIndex":{"type":"string"}}},"search":{"properties":{"columns":{"type":"string"},"description":{"type":"string"},"hits":{"type":"integer"},"kibanaSavedObjectMeta":{"properties":{"searchSourceJSON":{"type":"string"}}},"sort":{"type":"string"},"title":{"type":"string"},"version":{"type":"integer"}}}},"settings":{"index":{"creation_date":"1454537508624","number_of_shards":"1","number_of_replicas":"1","uuid":"Qkf4LIW8Q5iL84xLSqAqfg","version":{"created":"2020099"}}},"warmers":{}}}

If I try with curl here are the result :

With the root user:

curl -XPOST 'http://root:[email protected]:9200/_mget' -d '{"docs":[{"_index":".kibana","_type":"config","_id":"4.4.0"}]}'

{"docs":[{"_index":".kibana","_type":"config","_id":"4.4.0","_version":2,"found":true,"_source":{"buildNum":9689,"defaultIndex":"netflow-*"}}]}

With a standard user:

curl -XPOST 'http://dhr:[email protected]:9200/_mget' -d '{"docs":[{"_index":".kibana","_type":"config","_id":"4.4.0"}]}'

Forbidden path

The new version of Kibana is using /_msearch for every query so the index is not part of the URL path anymore.

I think that the way to implement the support of Kibana 4.4 is to match the content of the index field in the post request.

I've found an example here : https://templth.wordpress.com/2014/03/07/implementing-data-validation-in-elasticsearch/ but the java part is way above my head.

Do you think there is a way to implement somehting like this ?

Ps: I'm available if you need anything else to help you to solve the problem.

[README]web console which manages users provided in readme.md can not access.

Installed this plugin with elasticfence-2.1.1-SNAPSHOT.zip
After installation, the plugin path is $Elasticsearch_installation_path/plugins/elasticfence/

As the readme.md said, we should access the following: web console to manage users:
http://your.elasticsearch.hostname:9200/_plugin/http-user-auth-plugin/index.html
The result: Can not access.

Suggest to changed the web console:
http://your.elasticsearch.hostname:9200/_plugin/elasticfence/index.html

Do you have plan new release for elasticsearch-v5.2x , v5.3x v5.4x

HI.
i wonder if you have a plan for new release(for elasticsearch-v5.2x , v5.3x v5.4x)
i have tried to modify elasticsearch-http-user-auth for elasticsearch-v5.3.1 .
but it is difficult for me. there are many compile error. There are many changes to elasticsearch API (remove RestFilter, RestFilterChain, change xContent.createParser..etc.. )

Documentation on Kibana integration is misleading

The README says that you should put 'root' as the username in kibana.yml.

I ran into this: #2

  1. Add an index filter "/.kibana" to an user which you created on Elasticfence and you set in kibana.yml

You should probably mention this or something similar in the documentation.

I created a separate admin user and added a bunch of accessable indices for it, but still had 'root' in the kibana.yml which caused:

[INFO ][plugin.elasticfence      ] auth failed: /_mget

need url whitelist config

we have auto check program to enable the hosts if check the content of url "/alive.status" is "ok",
so we needurl whiltelist config in this plugin, can you help us?

Elasticsearch 2.4 Build

When trying to install elasticfence on a elasticsearch 2.4.1 it prints a compatibility error:

-> Installing from https://github.com/elasticfence/elasticsearch-http-user-auth/releases/download/v2.3.5/elasticfence-2.3.5-SNAPSHOT.zip...
Trying https://github.com/elasticfence/elasticsearch-http-user-auth/releases/download/v2.3.5/elasticfence-2.3.5-SNAPSHOT.zip ...
Downloading .............................................................DONE
Verifying https://github.com/elasticfence/elasticsearch-http-user-auth/releases/download/v2.3.5/elasticfence-2.3.5-SNAPSHOT.zip checksums if available ...
NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Plugin [elasticfence] is incompatible with Elasticsearch [2.4.1]. Was designed for version [2.3.5]

Restricting Indices Access to Kibana Users

Hi,

I have created 3 kibana users namely admin, user1 and user2. while admin will have access to all indices in ES, user1 / user2 will have access to specific indices only.

I have whitelisted the IP address so that kibana can communicate with the ES without any issues and it is working fine. I can pump data in ES and read without any issues.

Now coming to Kibana UI, I can login as admin and see data belonging to all the indices. perfect. But when i login as user1 /user2, it is not restricting the data according to the indices. I have specified the indices using the user management console at _plugin/elasticfence/ for the users like

/[INDEX_NAME_1],/.kibana for user1
/[INDEX_NAME_2]
,/.kibana for user2

In this case, i expect user1 not to see the data in [INDEX_NAME_2] and user2 not to see the data in [INDEX_NAME_1]

Am i doing something wrong here ? or do i have to specify the index filter somewhere in the config file ?

Any inputs on this is greatly appreciated.

Thanks.

Problem while installing "EPERM: operation not permitted"

Hello!
I have a problem while installing plugin kibana-auth-plugin.
In console I got this message:

Plugin installation was unsuccessful due to error "EPERM: operation not permitted, rename 'D:\elastic_kibana\kibana-4.6.2-windows-x86\installedPlugins.plugin.installing' -> 'D:\elastic_kibana\kibana-4.6.2-windows-x86\installedPlugins\kibana-auth-plugin'"

Have can I fix this?
Thanks!

2.2.x ERROR: Could not find plugin descriptor

i can not install plugins in elasticsearch-2.2.0,and i have tried to install in several servers. it prompts Could not find plugin descriptor 'plugin-descriptor.properties' in plugin zip
,can you help me?

sudo bin/plugin install file:///usr/local/src/elasticsearch-2.2.0/elasticfence-2.2.0-SNAPSHOT.zip 
-> Installing from file:/usr/local/src/elasticsearch-2.2.0/elasticfence-2.2.0-SNAPSHOT.zip...
Trying file:/usr/local/src/elasticsearch-2.2.0/elasticfence-2.2.0-SNAPSHOT.zip ...
Downloading .DONE
Verifying file:/usr/local/src/elasticsearch-2.2.0/elasticfence-2.2.0-SNAPSHOT.zip checksums if available ...
NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Could not find plugin descriptor 'plugin-descriptor.properties' in plugin zip

Please - incompatible ES 2.3.5

I'm tried installing the pugin, but....

NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Plugin [elasticfence] is incompatible with Elasticsearch [2.3.5]. Was designed for version [2.3.4]

Thanks

a bug in UserData

org.elasticsearch.plugin.elasticfence.data.UserData.java

public UserData(String userName, String rawPassword, String... filters) {
setUsername(userName);
setPassword(rawPassword);
SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ssZZ");
setCreated(sdf.format(new Date()));
if (filters == null) { // TODO , this should be "filters != null"
Set filterSet = Sets.newConcurrentHashSet(Arrays.asList(filters));
setFilters(filterSet);
} else {
Set filterSet = Sets.newConcurrentHashSet();
setFilters(filterSet);
}
}

cannot be used in es2.3.5

hi ,how about es2.3.5, i want to use this
bin/plugin install file:///vagrant/elasticfence-2.4.0-SNAPSHOT.zip
but it alerts like this

-> Installing from file:/vagrant/elasticfence-2.4.0-SNAPSHOT.zip...
Trying file:/vagrant/elasticfence-2.4.0-SNAPSHOT.zip ...
Downloading .DONE
Verifying file:/vagrant/elasticfence-2.4.0-SNAPSHOT.zip checksums if available ...
NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Could not find plugin descriptor 'plugin-descriptor.properties' in plugin zip

Issues with index parameter

Hello, we are having an issue with accessing an index for a new user we generated. After generating the user, we are trying to give the user permissions with "curl -u root:rootpassword ’http://port/_httpuserauth?mode=updateindex&username=someuser&index=/_search* ".

However, we are getting a 403 forbidden message when we hit the api url ending in /api/elastic/_search?size=6.

However, if we use index=/_* it works fine. So either the regex is not working well for us or we don't know what to pass into the index. Any advice as to what we should be passing to index to make the permissions work?

Is there a way to print out the indices to see what exists?

Thank you!

Snapshot for ES 2.4.2

Hi,

I have ES 2.4.2. Is there a snapshot for ES 2.4.2 available ? I tried installing the 2.4.1 which is giving me compatibility issues.

Any help on this is appreciated.

Thanks !

Error installing 5.0.0 plugin on Windows

Just trying to install this plugin for the first time on Windows with this command:

bin/elasticsearch-plugin install https://raw.githubusercontent.com/elasticfence/elasticsearch-http-user-auth/5.0.0/jar/elasticfence-5.0.0-SNAPSHOT.zip

(I think the ReadME file has the outdated command of "plugin". It is now "elasticsearch-plugin" on ES 5.)

I keep getting this error after it is downloaded:
ERROR: elasticsearchdirectory is missing in the plugin zip

Any ideas? I'm sure I'm doing something wrong.

Thanks,
Steve

incompatible with version 5.5.0

Hell,

Am using ElasticSearch 5.5.0 Version and trying to install elasticfence-5.1.2 and got incompatible version error .
image

Regards
Uday

Authentication Problem

i installed elasticsearch-http-user-auth for elasticsearch 2.3.4 . At first time every thing was working fine.
when i query my elasticsearch node through curl using query "curl localhost:9200" it asked me for user name and password and shows "Needs Basic Auth" .
when provided with password it works fine
curl -u root:rootpasswo0d localhost:9200
returned
{
"name" : "Conquer Lord",
"cluster_name" : "elasticsearch",
.............
},
"tagline" : "You Know, for Search"
}

but when i query the same node through my chrome browser for first time it ask for username and password but not for second time ,or there after.

i tried restarting the elastic node but it sill does not ask for username and password.

Empowering Non-Root Users

Two questions:
a) Right now, I still see my Elasticsearch log show this:

[plugin.elasticfence ] Invalid User: /_cluster/health
[plugin.elasticfence ] Invalid User: /_cluster/stats

I use root:rootpassword in Logstash, KIbana and Marvel (coz, Root is the most empowered user with no restrictions on access). I wonder why I get those Invalid User messages.

b) Can we assign a Non-Root User the same privileges as that of a Root User?I want a non root user to be able to see marvel, kibana and everything else without any restriction. How can I accomplish this?

Maintaining the project

Hi @lmangani @ryanlutgen @tomsearch @digitalkaoz @AymanDF @kmels

I like the plugin simplicity and ease of use. While the project is currently unmaintained there still interesting for a lot of people to use. Given these points I would like to work on it and add support for current ELK versions.

But first my knowledge about porting and supporting elasticsearch plugins is a bit limited for that reason I would like some guidance like docs to read, java classes to reimplement and so on.

Thanks all and happy hacking as usual 😄

Can't work on Elasticsearch 2.1.1

Exception in thread "main" java.lang.IllegalArgumentException: Plugin [http-user-auth-plugin] is incompatible with Elasticsearch [2.1.1]. Was designed for version [2.0.0]
at org.elasticsearch.plugins.PluginInfo.readFromProperties(PluginInfo.java:117)
at org.elasticsearch.plugins.PluginsService.getPluginBundles(PluginsService.java:302)
at org.elasticsearch.plugins.PluginsService.(PluginsService.java:108)
at org.elasticsearch.node.Node.(Node.java:146)
at org.elasticsearch.node.Node.(Node.java:128)
at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:145)
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:178)
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:285)
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35)
Refer to the log for complete error details.

how to fix it ?

License Request

hi

Under what type of license the opensource elasticsearch-http-user-auth is distributed. I would appreciate and full license terms of usage.

regards
Ahzam

Auth is not working on production after installing elasticsearch-http-user-auth

Hi
I am able to access elastic search without a credential on production, the same thing I tried on Dev/stage instances there worked fine.

On Dev

Elasticsearch v 5.1.2
Elasticsearch-http-user-auth v5.1.2
java version "1.8.0_45"

curl http://localhost:9200/_cluster/health?pretty
Needs Basic Auth

curl -u root:root http://localhost:9200/_cluster/health?pretty
Success

On Production

Elasticsearch v 5.1.2
Elasticsearch-http-user-auth v5.1.2
java version "1.8.0_111"

curl http://localhost:9200/_cluster/health?pretty
Success
Failure : I am able to access without a credential actual it should not.

curl -u root:root http://localhost:9200/_cluster/health?pretty
Success

Can you help me to solve this problem?
Did I miss any configuration?

Kibana can not be set up when set a non-root user for elasticsearch.username in kibana.yml

Steps to reproduce:

  1. add user and index:
    {"username":"admin","password":"045928218d6d5a42f976163d70cdfe9226e9d1c3ea6bf1647ae1d8f44c2edc7d","indices":["/.kibana"],"created":"2016-07-08T03:35:13-0400"},
  2. Modify the kibana.yml, add the following info:
    elasticsearch.username: "admin"
    elasticsearch.password: "somepass"
  3. Start Kibana and show error info:
    log [05:35:56.789] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready
    log [05:35:56.844] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch
    log [05:35:56.872] [error][elasticsearch] Request error, retrying -- Parse Error
    log [05:35:56.878] [info][status][plugin:kbn_vislib_vis_types] Status changed from uninitialized to green - Ready
    log [05:35:56.885] [info][status][plugin:markdown_vis] Status changed from uninitialized to green - Ready
    log [05:35:56.893] [warning][elasticsearch] Unable to revive connection: http://xx.xx.xx.xx:9200/
    log [05:35:56.894] [warning][elasticsearch] No living connections

    log [05:35:56.897] [error][status][plugin:elasticsearch] Status changed from yellow to red - Unable to connect to Elasticsearch at http://xx.xx.xx.xx:9200. Retrying in 2.5 seconds.
    log [05:35:56.899] [info][status][plugin:metric_vis] Status changed from uninitialized to green - Ready
    log [05:35:56.905] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready
    log [05:35:56.910] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready
    log [05:35:56.915] [info][status][plugin:table_vis] Status changed from uninitialized to green - Ready
    log [05:35:56.933] [info][listening] Server running at http://0.0.0.0:5601
    log [05:35:59.405] [warning][elasticsearch] Unable to revive connection: http://xx.xx.xx.xx:9200/
    log [05:35:59.406] [warning][elasticsearch] No living connections
    log [05:36:01.914] [warning][elasticsearch] Unable to revive connection: http://xx.xx.xx.xx:9200/
    log [05:36:01.916] [warning][elasticsearch] No living connections

But with the root user, can start kibana successfully.
elasticsearch.username: "root"
elasticsearch.password: "rootpass"

Marvel Error Due to Elasticfence

Two issues:

a) Each time I make a change in the Elasticsearch.yml file (any configuration setting), and I restart Elasticsearch and Kibana, when I attempt to log on to Marvel, I get this "Marvel: Error 400 Bad Request: No Living Connections" error.

WHy do you think Marvel gets corrupted every time? Any template being set?

b) I still get to see "Invalid User: /_cluster/stats" "Invalid User: /_cluster/health" in the Elasticsearch logs file.

I infact added these two as users on the UI. But still they come up in the log file.

support for elasticsearch 5.2

I would like to use elasticfence for elasticsearch 5.2.0. Since elasticsearch can't install the plugin, I modified the elasticsearch related config in plugin-descriptor.properties to 5.2. Thus i am able to install the plugin. However starting elasticsearch fails with the following error:

Caused by: java.lang.ClassNotFoundException: org.elasticsearch.rest.RestFilter
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[?:1.8.0_131]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[ 

I couldn't find the rest directory/class in the org.elasticsearch package. Can you please suggest how to fix this issue or make elasticfence work for elasticsearch-5.2

kibana 5 authentication plugin

Hi.
Is there any plan of releasing a kibana 5.1.2 authentication plugin any time soon? as there was for kibana 4?

Thanks

How to test the user have the index permission

I have install the plugin suscess. but when i set the user have the index permisson,how can i to check the set successful with java API? how can i set the username and password with java API?

default

(remark :i have check with curl -u ... ,it is all right)

at the same time ,can give an exampe about: "Other users can access URLs under their own indices that are specified with this plugin's API."

image

Elasticfence - Invalid User

I have installed the plugin "Elasticfence" (for Basic HTTP Auth for my ES 2.3.2). And wrote the following two lines in my elasticsearch.yml:

elasticfence.disabled: false
elasticfence.root.password: rootpassword

When I restart the cluster, I keep getting this over and over again in the log file:

[INFO ][plugin.elasticfence ] Invalid User: /_bulk
[INFO ][plugin.elasticfence ] Invalid User: /

What am I to do to avert this? Is there any setting I missed? Just FYI, I also have Logstash shoving logs into Elasticsearch. I mentioned the same username and password I added on the UI for Elasticfence in the Logstash Config File for output plugin of Elasitcsearch.

Error installing elasticsearch-http-user-auth-5.1.2.zip on Elasticsearch-5.1.2

I installed Elasticsearch 5.1.2 using the elasticsearch-5.1.2.tar.gz.
Then I tried installing the plugin on this instance using the following command -
./elasticsearch-plugin install file:///scratch/dumakant/downloads/elasticsearch-http-user-auth-5.1.2.zip

But was seeing following error -

-> Downloading file:///scratch/dumakant/downloads/elasticsearch-http-user-auth-5.1.2.zip
[=================================================] 100%  
ERROR: elasticsearch directory is missing in the plugin zip

Elasticfence 2.3.2

I have ES 2.3.2 running and the existing plugin (Elasticfence 2.3.1) doesn't seem to work with it. When can I expect Elasticfence 2.3.2 to be rolled out?

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.