2017-11-16 11:50:35 simo jhrozek: I just installed sssd-kcm
2017-11-16 11:50:46 simo it dropped a file in krb5.conf.d that enables it
2017-11-16 11:50:57 simo but my user was still using KEYRING (issue 1)
2017-11-16 11:51:07 -- tscherf is now known as tscherf|afk
2017-11-16 11:51:15 simo jhrozek: so I entered as root and removed the sss db and restarted sssd
2017-11-16 11:51:22 simo jhrozek: my users started to fail to auth
2017-11-16 11:51:33 simo debug logs said KCM was not working (issue 2)
2017-11-16 11:51:55 simo checked with systemctl and it said sssd-kcm.socket is enabled, but the dameon is daed
2017-11-16 11:51:58 simo (issue 3)
2017-11-16 11:52:08 sbose simo, I'll bbiab
2017-11-16 11:52:16 simo so I now manually started (and enabled) the sssd-kcm service
2017-11-16 11:52:29 simo sbose: sure, lemme know the answer when back
2017-11-16 11:52:38 simo jhrozek: and now sssd-kcm seem to be working
2017-11-16 11:52:57 simo jhrozek: so main q. is, why sssd-kcm fails to work when socket-enabled ?
2017-11-16 11:53:24 jhrozek simo: which version do you use?
2017-11-16 11:54:11 simo jhrozek: I installed whatever is in F27 now
2017-11-16 11:55:04 simo jhrozek: 1.16.0-2.fc27
2017-11-16 11:55:32 jhrozek hm, that one should be fixed
2017-11-16 11:55:38 jhrozek * Fri Nov 03 2017 Lukas Slebodnik lslebodn@fedoraproject.org - 1.16.0-2 - Resolves: upstream#3529 - sssd-kcm Fix restart during/after upgrade
2017-11-16 11:55:40 simo jhrozek: for now other than this start issue (and the keyring reuse issue) it seem to be working.
2017-11-16 11:55:53 simo jhrozek: it was not an upgrade
2017-11-16 11:56:09 simo jhrozek: it was an install, I had no sssd-kcm installed on this machine before
2017-11-16 11:56:13 jhrozek I see
2017-11-16 11:58:18 jhrozek I guess I need to try a clean install, because on my machine the socket is enabled and running:
2017-11-16 11:58:29 jhrozek Loaded: loaded (/usr/lib/systemd/system/sssd-kcm.socket; enabled