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

authconfig is still failing on first run if sssd is not enabled, and Kerberos is #40

Open
nkadel-skyhook opened this issue Oct 31, 2016 · 4 comments

Comments

@nkadel-skyhook
Copy link

When LDAP is not enabled, and Kerberos, the sssd.conf file is being updated with Kerberos configurations. But the sssd daemon should not, and on CentOS 6 and 7 cannot run. So the first chef run enabling Kerberos fails because of an attempt to restart sssd, which is a disabled daemon due to the other settings made by authconfig.

You and I have discussed this before: it's still a confusing bug to most. Running chef twice because that ignores broken operations under the first run is not a good approach to configuring security related software.

@jcam
Copy link
Owner

jcam commented Oct 31, 2016

agreed, not a good approach at all.
I'm waiting for @Sauraus who already went to the trouble of merging a few of the different PRs that add 7 support, fix some of these bugs, etc... he's testing it now. Maybe he has his version available somewhere and we can all get to testing it...
#35

@Sauraus
Copy link
Contributor

Sauraus commented Jan 13, 2017

I believe this P4 solves the CentOS 7 & ldap problem because I have the very same setup: #41

@jcam
Copy link
Owner

jcam commented Mar 21, 2017

merged #41 which should resolve this

@jcam
Copy link
Owner

jcam commented Apr 3, 2017

i'm seeing weird issues with nslcd in this version.. hmm...

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

No branches or pull requests

3 participants