On Thu, Feb 06, 2020 at 03:05:13PM +0000, Ondrej Valousek wrote:
did you try refreshing the machine password in AD?Looks like it's
too old.
O.
________________________________
From: David David <modrik(a)seznam.cz>
Sent: Thursday, February 6, 2020 12:09 PM
To: sssd-users(a)lists.fedorahosted.org <sssd-users(a)lists.fedorahosted.org>
Subject: [SSSD-users] sssd 1.16.4. ADV190023.
Hello,
i guess that you probably heard about ADV190023. Our AD admin told me that linux servers
which are under my responsibility send an unsigned request to AD, what could be a problem
related to this incomming Ad patch:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport....
I am using sssd in "sssd-ad mode." The communication between a linux servers
and our AD is crypted by kerberos, so this should be ok.
I found only one kind of request which could result in potential failure. After mentioned
patching implementation. See please below:
(Wed Feb 5 16:57:21 2020) [sssd[be[AD]]] [be_ptask_execute] (0x0400): Task [AD machine
account password renewal]: executing task, timeout 60 seconds
(Wed Feb 5 16:57:21 2020) [sssd[be[AD]]] [be_ptask_done] (0x0400): Task [AD machine
account password renewal]: finished successfully
(Wed Feb 5 16:57:21 2020) [sssd[be[AD]]] [be_ptask_schedule] (0x0400): Task [AD machine
account password renewal]: scheduling task 86400 seconds from last
Hi,
Ondrej is right, those messages are related to adcli trying to update
the machine account password if it is too old. To check when the
password was last updated adcli uses LDAP with SASL/GSSAPI. I've added a
patch so that SASL/GSS-SPNEGO is used when it is available in the AD DC
side
https://gitlab.freedesktop.org/realmd/adcli/commit/a6f795ba3d6048b32d7863...
With SASL/GSS-SPNEGO all requirements are negotiated automatically and
signing should be switched on if required.
With SASL/GSSAPI you might be able to tune this manually, see e.g. the
SASL and GSSAPI options in man ldap.conf for details.
There is also a patch for adcli which tells adcli to use ldaps
https://gitlab.freedesktop.org/realmd/adcli/commit/85097245b57f190337225d...
but this is currently not used by SSSD. And in general I think using
GSS-SPNEGO is sufficient since there is no requirement to switch to
ldaps (if I read the advisory correctly) and AD does not enable ldaps by
default as well.
bye,
Sumit
Everytime, this task is executed, our AD write into its log that an unsighned request
came from my linux server. I tried to set ldap_tls_cert and ldap_tls_key into sssd.conf
which point to the cert and key generated by our AD, but without success.
I tried to find a proper solution how to sign the request that AD stop complaining, but
nothing usefull found.
My question is. Should I be affraid that after the patching, our AD will stop to
communicate with my linux servers?
Really thanks in advance for your answer. I really appreciate your effort.
_______________________________________________
sssd-users mailing list -- sssd-users(a)lists.fedorahosted.org
To unsubscribe send an email to sssd-users-leave(a)lists.fedorahosted.org
Fedora Code of Conduct:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fe...
List Guidelines:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedorap...
List Archives:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.f...
_______________________________________________
sssd-users mailing list -- sssd-users(a)lists.fedorahosted.org
To unsubscribe send an email to sssd-users-leave(a)lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/sssd-users@lists.fedorahoste...