Hi, same problem is on sssd, when I upgrade from 2.5.2 to 2.6.1,
probably the bug is not adcli related.
I tried to unjoin because I had some authentication problems, in
/var/log/sssd/sssd_<MYDOMAIN>.log
* (2022-01-02 0:01:25): [be[MYDOMAIN]] [sasl_bind_send] (0x0100):
Executing sasl bind mech: GSS-SPNEGO, user: PCLEONOVO$
* (2022-01-02 0:01:25): [be[MYDOMAIN]] [ad_sasl_log] (0x0040):
SASL: No worthy mechs found
********************** BACKTRACE DUMP ENDS HERE
*********************************
(2022-01-02 0:01:25): [be[MYDOMAIN]] [sasl_bind_send] (0x0020):
ldap_sasl_interactive_bind_s failed (-6)[Unknown authentication method]
(2022-01-02 0:01:25): [be[MYDOMAIN]] [sdap_cli_connect_recv] (0x0040):
Unable to establish connection [1432158227]: Authentication Failed
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING
BACKTRACE:
* (2022-01-02 0:01:25): [be[MYDOMAIN]] [sasl_bind_send] (0x0020):
ldap_sasl_interactive_bind_s failed (-6)[Unknown authentication method]
* (2022-01-02 0:01:25): [be[MYDOMAIN]] [sasl_bind_send] (0x0080):
Extended failure message: [SASL(-4): no mechanism available: No worthy
mechs found]
* (2022-01-02 0:01:25): [be[MYDOMAIN]] [sdap_cli_connect_recv]
(0x0040): Unable to establish connection [1432158227]: Authentication Failed
********************** BACKTRACE DUMP ENDS HERE
*********************************
now, when i try to join again:
* Using GSS-SPNEGO for SASL bind
! Couldn't authenticate to active directory: SASL(-4): no mechanism
available: No worthy mechs found
adcli: couldn't connect to MYDOMAIN domain: Couldn't authenticate to
active directory: SASL(-4): no mechanism available: No worthy mechs found
! Insufficient permissions to join the domain
realm: Couldn't join realm: Insufficient permissions to join the domain
