New sssd.conf variable ad_use_ldaps not working. On starting sssd it errors with "sssd[be[13765]: Could not start TLS encryption. (unknown error code)"
# lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Note: problem also seen with Ubuntu 20.04.2
# apt-cache policy sssd | grep Installed
Installed: 1.16.1-1ubuntu1.7
Problem
Added a working Public root CA cert to the common ca-certificate (/etc/ssl/ca-certificates) and /etc/ldap/ldap.conf has following set:
TLS_CACERT /etc/ssl/certs/ca-certificates.crt
An ldapsearch using the above certificate bundle against LDAPS is successful:
New sssd.conf variable ad_use_ldaps not working. On starting sssd it errors with "sssd[be[13765]: Could not start TLS encryption. (unknown error code)"
# lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Note: problem also seen with Ubuntu 20.04.2
# apt-cache policy sssd | grep Installed
Installed: 1.16.1-1ubuntu1.7
Expectation /bugs.launchpad .net/ubuntu/ focal/+ source/ sssd/+bug/ 1868703/
Adding ad_use_ldaps to a working AD integrated /etc/sssd/sssd.conf to use port 636 instead of port 389 due ADV 190023. Reference https:/
Problem ca-certificates ) and /etc/ldap/ldap.conf has following set: certs/ca- certificates. crt
Added a working Public root CA cert to the common ca-certificate (/etc/ssl/
TLS_CACERT /etc/ssl/
An ldapsearch using the above certificate bundle against LDAPS is successful:
# openssl s_client -connect company- ad-server. company. com:636 CONNECTED(00000005) /company- ad-server. company. com:636 -b "dc=company,dc=com" "(sAMAccountNam e=superduperuse r)" ldap_initialize( ldaps:/ /company- ad-server. company. com:636/ ??base ) SASL/GSSAPI authentication started SASL username: <email address hidden> SASL SSF: 0 filter: (sAMAccountName =superduperuser ) requesting: All userApplication attributes <snip> Internal, OU=Users, OU=Admin, DC=company, DC=com <snip>
# ldapsearch -v -H ldaps:/
# Duperuser\2C Super ADM, Users, Admin, company.com dn: CN=Duperuser\, Super ADM,OU=
sssd.conf is configured with:
[sssd]
domains = company.com
config_file_version = 2
services = nss, pam
[domain/ company. com] password_ if_offline = True qualified_ names = True certs/ca- certificates. crt
ad_domain = company.com
krb5_realm = company.com
realmd_tags = manages-system joined-with-adcli
cache_credentials = True
id_provider = ad
krb5_store_
default_shell = /bin/bash
use_fully_
fallback_homedir = /home/%u@%d
ldap_id_mapping = True
ad_use_ldaps = True
ldap_tls_cacert = /etc/ssl/
auth_provider = ad
access_provider = simple
simple_allow_groups = linux-admins
Stopping sssd, clearing sssd cache, starting sssd returns following error:
sssd[be[13765]: Could not start TLS encryption. (unknown error code)
Setting debug_level = 4 (or higher) returns following around this unknown error: common_ status] (0x0100): Marking server 'ad-server. company. com' as 'name resolved' server_ process] (0x0200): Found address for server ad-server. company. com: [y.y.y.y] TTL 3600 callback] (0x0100): Constructed uri 'ldaps: //ad-server. company. com' callback] (0x0100): Constructed GC uri 'ldaps: //ad-server. company. com' socket_ init_send] (0x0400): Setting 6 seconds timeout for connecting init_sys_ connect_ done] (0x0020): ldap_install_tls failed: [Connect error] [(unknown error code)] init_state_ destructor] (0x0400): calling ldap_unbind_ext for ldap:[0x55d1149 ef6e0] sd:[18] init_state_ destructor] (0x0400): closing socket [18] connect_ done] (0x0020): sdap_async_ connect_ call request failed: [5]: Input/output error. port_status] (0x0100): Marking port 389 of server 'ad-server. company. com' as 'not working' port_status] (0x0400): Marking port 389 of duplicate server 'ad-server. company. com' as 'not working'
[set_server_
[be_resolve_
[ad_resolve_
[ad_resolve_
[sssd_async_
[sss_ldap_
[sss_ldap_
[sss_ldap_
[sdap_sys_
[fo_set_
[fo_set_