Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

provide basic auth capabilities to elasticsearch plugin #2065

Closed
wants to merge 1 commit into from
Closed

provide basic auth capabilities to elasticsearch plugin #2065

wants to merge 1 commit into from

Conversation

Crapworks
Copy link
Contributor

Required for all PRs:

  • CHANGELOG.md updated (we recommend not updating this until the PR has been approved by a maintainer)
  • Sign CLA (if not already signed)
  • README.md updated (if adding a new plugin)

PR #1970 was closed because there were two different issues in it and it should be split. Since we are also using Shield and need basic authentication for the plugin to work, I extracted the relevant parts and made a new PR.

Regards,
Christian

@sparrc sparrc added this to the 1.2.0 milestone Nov 22, 2016
@phemmer
Copy link
Contributor

phemmer commented Nov 22, 2016

What about putting the credentials in the URL instead of separate parameters?
All the official clients support the scheme, while only some of them support user/pass as separate parameters, and the parameters vary at that, thus URL might be considered more standard.
https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/auth-reference.html
https://www.elastic.co/guide/en/elasticsearch/client/php-api/current/_security.html

Just a thought. :-)

@somnair
Copy link

somnair commented Nov 22, 2016

Thanks @Crapworks for creating a new PR . @phemmer nice idea . i can give that a try :)

@Crapworks
Copy link
Contributor Author

Crapworks commented Nov 23, 2016

@phemmer that actually works! Haven't thought about that. In this case, there should just be a comment that is mentioning that possibility in the config. Wan't me to create a new PR for that?

@sparrc
Copy link
Contributor

sparrc commented Nov 23, 2016

sure, or just update this PR with a force push

@Crapworks
Copy link
Contributor Author

@sparrc Done

@sparrc
Copy link
Contributor

sparrc commented Dec 9, 2016

closed by efb64a0

@sparrc sparrc closed this Dec 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants