Using keystore in curator

Hi There,

Does anyone use Curator where the username and password are stored in a keystore rather than being plain text in the config file. I need to try and avoid passwords in plain text in configuration files.

Any suggestions would be helpful.

This functionality does not yet exist in Curator, but has been requested.

Thank you theuntergeek.

Do you know what permissions a user needs to run curator. I would like to limit the user to have the permissions necessary to run curator and nothing else.

Curator itself needs no permissions other than outbound TCP access to the cluster IP and port.

However, if you have Security enabled in your cluster, the user Curator connects to the cluster as must have the proper roles/permissions for the actions being executed.

Thank you for letting me know.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.