gem icon indicating copy to clipboard operation
gem copied to clipboard

Gem with shield

Open Akhilesh-Anb opened this issue 8 years ago • 11 comments

Elasticsearch is secured with shield and GEM is repeatedly asking me the credentials and unable to connect

Akhilesh-Anb avatar Apr 06 '17 21:04 Akhilesh-Anb

@Akhilesh-Anb GEM would create a request with the Basic Auth header based on the username:password you pass along in the URL. I don't think the fact that you are using Shield should cause a problem. It could be something else, but then we would need to look at the console.log and the network tab.

Are you able to cURL into your Elasticsearch instance using the username:password that you are passing to GEM?

siddharthlatest avatar Apr 06 '17 21:04 siddharthlatest

curl -u akhil:akhil@789 -XGET 3.4.86.234:9200

Its not giving me any response from commandline

Akhilesh-Anb avatar Apr 06 '17 21:04 Akhilesh-Anb

@Akhilesh-Anb That can likely mean some issue with your Shield configuration.

siddharthlatest avatar Apr 06 '17 21:04 siddharthlatest

but when i do 3.4.86.234:9200 with those credentials it works for me... why not for GEM

Akhilesh-Anb avatar Apr 06 '17 21:04 Akhilesh-Anb

While using it as a extension i got this proble.. even i installed it as a plugin, i'm still facing this

Can you suggest me what configuration i need to look at

Akhilesh-Anb avatar Apr 06 '17 21:04 Akhilesh-Anb

@Akhilesh-Anb

curl -u akhil:akhil@789 -XGET 3.4.86.234:9200

Its not giving me any response from commandline

If you are not getting a response from cURL, that likely points the issue to something on the Elasticsearch / Shield side of things.

but when i do 3.4.86.234:9200 with those credentials it works for me... why not for GEM

Are you saying that you can access it from a browser tab directly but not from GEM? That also doesn't tell why you can't access it via cURL.

siddharthlatest avatar Apr 06 '17 21:04 siddharthlatest

Now i'm able to get output from CURL

[root@aocapld0056a ~]# curl -u akhil:akhil@999 -XGET 3.4.86.234:9200 { "name" : "NODE_1", "cluster_name" : "dev", "version" : { "number" : "2.3.5", "build_hash" : "90f439ff60a3c0f497f911e64ccd01edbb4", "build_timestamp" : "2016-07-27T10:36:52Z", "build_snapshot" : false, "lucene_version" : "5.5.0" }, "tagline" : "You Know, for Search" }

Even now its asking repeatedly while accessing GEM

Akhilesh-Anb avatar Apr 06 '17 22:04 Akhilesh-Anb

http://akhil:akhil%[email protected]:9200 in the browser is responding.... But in GEM its asking me credentials repeatedly

Akhilesh-Anb avatar Apr 06 '17 22:04 Akhilesh-Anb

Hi @siddharthlatest ... I have two clusters

The cluster which is having credential akhil:akhil is working with GEM

The cluster which is having credentials akhil:akhil@999 is not working with GEM ( @ is becoming problem)

Any solution for this?

Akhilesh-Anb avatar Apr 06 '17 23:04 Akhilesh-Anb

@Akhilesh-Anb You might be right, @ is typically a reserved character in the URL. Since we pass credentials in GEM as a part of the URL, it might be causing an issue. Can you try with using only URL safe characters - http://stackoverflow.com/a/695467/1221677?

siddharthlatest avatar Apr 07 '17 06:04 siddharthlatest

I mentioned in URL as http://akhil:akhil"@"[email protected]:9200

Its not working, when i debug its taking the URL as GET http://%22dm1n:9200/spot-lite-new/_settings

Akhilesh-Anb avatar Apr 07 '17 11:04 Akhilesh-Anb