-
Notifications
You must be signed in to change notification settings - Fork 210
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
Erchef dumps LDAP password #156
Comments
@Roviluca Thanks for the bug report. Our support team (support@chef.io) should be able to help you fix up your existing users. I'll take a look at whether there is a way we can surpress this info even in the case of a bad user record. |
The problem that was affecting the chef server was that inside the user information there was 'null' value into the external user account, we solved that by backing up all the users and looking at all parameters.
|
@Roviluca Yup. Support would have take you more or less through the same procedure. I believe that we fixed the bug that can put users in that state, but because we don't know what the external_authentication_uid is supposed to be, existing users are still affected. Glad you got it sorted out. |
@stevendanna I'm running Chef Server 12.1.0 and erchef still logs the password when logging into a broken user account. |
@jeremiahsnapp Correct, we haven't fixed the underlying problem with the LDAP password still being dumped in the case of broken accounts, which is why this bug is still open. |
This is resolved with #900 |
Hello,
i have upgrade our standalone chef server 12.0.2 to 12.0.8 along with opscode-manage in order to fix bug #66 . After the upgrade, we will still getting the 500 error for the existing users, while troubleshooting the problem we found out that the password was dumped into the logs.
Below i pasted the logs (i removed the passwords).
The text was updated successfully, but these errors were encountered: