Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionNikhil Suryawanshi
2021-12-16 15:18:10 UTC
Description of problem:
Authentication for AD users works but a backtrace has been triggered due to below error message:
[write_krb5info_file_from_fo_server] (0x0020): [RID#73501] There is no server that can be written into kdc info file.
Version-Release number of selected component (if applicable):
sssd version : 2.5.2-2.el8_5.1.x86_64
Comments from Sumit:
```
I think it might be possible to reach the error message in the AD
provider if only a Global Catalog server is in the server list and this
is filtered out. This might happen after some inactivity where
connections are closed and a new request triggers at first a Global
catalog lookup.
```
```
Global Catalog servers can come from any domain in the forest and
for the kdcinfo file for domainA we only want KDCs from domainA to be
present.
But there should be a special failover service (AD_GC) for the Global Catalog
servers. For this service the AD provider should not try to create the
kdcinfo files at all.
Tomas, can you check if this is the case (AD provider tries to create a
kdcinfo file when the failover service is AD_GC) and if yes add code to
skip it?
```
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (sssd bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:7739