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

Allow disabling Uchiwa authentication #57

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

thomasriley
Copy link

To disable authentication in Uchiwa you simply remove the user and pass keys in the Uchiwa configuration. This change prevents null set node['uchiwa']['settings'] attributes from being included in /etc/sensu/uchiwa.json. Therefore, to disable authentication simply set the user and pass Chef attributes to nil.

…s possible to disable authentication using this cookbook
Copy link
Contributor

@majormoses majormoses left a comment

Choose a reason for hiding this comment

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

I'd strongly oppose actually using a setup without authentication, I think we should minimally log a warning that this is a bad idea.

@@ -21,7 +21,7 @@
# Generate config file
settings = {}
node['uchiwa']['settings'].each do |k, v|
settings[k] = v
settings[k] = v unless v.nil?
Copy link
Contributor

@majormoses majormoses Aug 6, 2017

Choose a reason for hiding this comment

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

This makes it possible to not specify required config, I'd opt to a check on k and look for the specific ones (username,password, etc) to allow being nil and then check those for nil and warn on them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants