Comment 0 for bug 1893438

Tested on Ubuntu Desktop 20.04.1 and Groovy up-to-date.

The setup in one ADC running on Windows Server 2019 and 3 clients, Ubuntu Desktop 20.04.1, Ubuntu Deskop Groovy, Fedora 32.

On Ubuntu clients, after following the documentation at https://discourse.ubuntu.com/t/service-sssd/11579 to connect AD with sssd and realmd, it is not possible to resolve users (id, getent, login, ...) without creating the file /etc/krb5.conf manually.

The documentation mentions that realmd should take care of the configuration. The sssd configuration is generated correctly and identical to Fedora.

Joining the domain with "realm join" works fine and the temporary kerberos config file created by realmd is correct.

In the logs there 2 errors but likely linked, showing that the AD provider is offline.
""""

[sssd[be[warthogs.biz]]] [sasl_bind_send] (0x0080): Extended failure message: [SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Configuration file does not specify default realm)]

""""

[sssd[be[warthogs.biz]]] [get_server_status] (0x1000): Status of server 'adc01.warthogs.biz' is 'name resolved'
[sssd[be[warthogs.biz]]] [get_port_status] (0x1000): Port status of port 0 for server 'adc01.warthogs.biz' is 'not working'
[sssd[be[warthogs.biz]]] [get_port_status] (0x0080): SSSD is unable to complete the full connection request, this internal status does not necessarily indicate network port issues.
[sssd[be[warthogs.biz]]] [fo_resolve_service_send] (0x0020): No available servers for service 'AD'
[sssd[be[warthogs.biz]]] [sdap_id_release_conn_data] (0x4000): releasing unused connection
[sssd[be[warthogs.biz]]] [be_resolve_server_done] (0x1000): Server resolution failed: [5]: Input/output error
[sssd[be[warthogs.biz]]] [sdap_id_op_connect_done] (0x0020): Failed to connect, going offline (5 [Input/output error])
[sssd[be[warthogs.biz]]] [be_mark_offline] (0x2000): Going offline!

""""

It works fine on Fedora 32 and using realmd to join, is enough to be able to resolve the users. Besides, the errors mentioned above are not displayed in the logs.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: sssd 2.2.3-3
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 28 10:05:25 2020
InstallationDate: Installed on 2020-08-27 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: sssd
UpgradeStatus: No upgrade log present (probably fresh install)