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

Updated the registry clusters entrypoint to support the use of custom username and password combinations #1224

Conversation

paulslaven
Copy link
Contributor

The current implementation of the register clusters entrypoint sets the password to "admin" in the credentials file and fails on authentication if any other username/password combination is used. This value is picked up by the get_password method in the spreaper, as this finds the value in the file, and thus attempts authentication with this hard coded value.

This PR maintains the default support for the default username and password while allowing those who change the username/password for the Cassandra Reaper to also use these via environment variable (REAPER_AUTH_USER and REAPER_AUTH_PASSWORD).

This would enable more flexible use of this register-cluster method while allowing better security though stronger credentials in its usage.

… username and password, maintained support for default admin credentials if values are not used
Copy link
Contributor

@adejanovski adejanovski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @paulslaven, LGTM 👍

@adejanovski adejanovski merged commit f221016 into thelastpickle:master Sep 12, 2022
@paulslaven
Copy link
Contributor Author

Great project @adejanovski, thanks for the review 👍

adejanovski pushed a commit that referenced this pull request Nov 3, 2022
… username and password, maintained support for default admin credentials if values are not used (#1224)
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.

None yet

2 participants