Learn more about these different git repos.
Other Git URLs
Note: Maybe this is not just GPO code issue, but so far I have only seen the effect in the GPO code
If the domain name part of the domain section in sssd is different then the actual AD domain name, we can use the ad_domain option to specify the name.
But GPO code does not respect the option and still uses the name from the domain section.
Reproducer: join AD domain using (using realmd) change the domain name part of the domain section in sssd.conf set GPO to enforcing login as AD user
When generating the target's DN SSSD uses the name from domain section name and login fails with system error.
Sounds like duplicate of https://pagure.io/SSSD/sssd/issue/3847
Metadata Update from @pbrezina: - Custom field design_review adjusted to on - Custom field mark adjusted to on - Custom field patch adjusted to on - Custom field review adjusted to on - Custom field sensitive adjusted to on - Custom field testsupdated adjusted to on - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4718
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.