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

ldap password in config file #173

Closed
df-cgdm opened this issue Nov 29, 2019 · 8 comments
Closed

ldap password in config file #173

df-cgdm opened this issue Nov 29, 2019 · 8 comments
Labels
help wanted Community contributions are especially encouraged for these issues.

Comments

@df-cgdm
Copy link

df-cgdm commented Nov 29, 2019

The bind password used for authentication and/or authorization is both readable in the config file and in Kibana.
It will be better to use a hash like for internal user password or to store the password with another mechanism like the elastic keystore.

@Luckyyyshot
Copy link

I'm having the same problem. I'm currently working on something with a requirement that no passwords must be in plain text. It might not give much more meaningful security in reality, but it will allow this system to conform to many countries regulations for no sensitive data to be found in plain text.

@df-cgdm
Copy link
Author

df-cgdm commented Apr 13, 2021

Any update?

@Luckyyyshot
Copy link

Luckyyyshot commented Apr 13, 2021

Not as far as I know sadly.

@df-cgdm
Copy link
Author

df-cgdm commented Dec 10, 2021

Hello any update on this ?
Another solution is also to store the ldap password in the keystore

@df-cgdm
Copy link
Author

df-cgdm commented Aug 22, 2022

Hello, any progress on this requirement?

@peternied peternied added the help wanted Community contributions are especially encouraged for these issues. label Aug 22, 2022
@peternied
Copy link
Member

No progress, but we'd gladly review a pull request for this functionality

@davidlago
Copy link

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).

If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.

Thanks!

@df-cgdm
Copy link
Author

df-cgdm commented Oct 18, 2022

This issue should still be considered (I have not enought skill to help you on this :) )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Community contributions are especially encouraged for these issues.
Projects
None yet
Development

No branches or pull requests

4 participants