-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gpo: use correct base dn #4840
Labels
Closed: Fixed
Issue was closed as fixed.
Comments
avisiedo
added a commit
to avisiedo/sssd
that referenced
this issue
May 25, 2020
Fixing some trailing characters that I forgot into the change. Resolves: SSSD#4840
avisiedo
added a commit
to avisiedo/sssd
that referenced
this issue
May 26, 2020
Fix whitespaces that remains into the changes yet. SSSD#4840
avisiedo
added a commit
to avisiedo/sssd
that referenced
this issue
May 29, 2020
GPO code in ad_gpo_connect_done converts domain name to base dn which may not be correct. For example if the domain name in sssd.conf is AD, computed base is then dc=AD, but the correct base dn is dc=ad,dc=vm. This makes gpo code to fail. Resolves: SSSD#4840
pbrezina
added a commit
to pbrezina/sssd
that referenced
this issue
Jul 9, 2020
Domain name in SSSD configuration does not have to be the same as the AD domain. GPO did not work in this case. Resolves: SSSD#4840
pbrezina
added a commit
to pbrezina/sssd
that referenced
this issue
Jul 9, 2020
Domain name in SSSD configuration does not have to be the same as the AD domain. GPO did not work in this case. Steps to reproduce: 1. Join SSSD to an AD domain (ad.vm) 2. Create GPO that is applicable to the host/user 3. Name the SSSD domain differently ([domain/AD]) 4. Try to authenticate as AD user Resolves: SSSD#4840
pbrezina
added a commit
to pbrezina/sssd
that referenced
this issue
Jul 23, 2020
Domain name in SSSD configuration does not have to be the same as the AD domain. GPO did not work in this case. Steps to reproduce: 1. Join SSSD to an AD domain (ad.vm) 2. Create GPO that is applicable to the host/user 3. Name the SSSD domain differently ([domain/AD]) 4. Try to authenticate as AD user Resolves: SSSD#4840
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3847
GPO code in
ad_gpo_connect_done
converts domain name to base dn which may not be correct. For example if the domain name insssd.conf
isAD
, computed base is thendc=AD
, but the correct base dn isdc=ad,dc=vm
. This makes gpo code to fail.Comments
Comment from jhrozek at 2018-10-11 15:34:11
Metadata Update from @jhrozek:
Comment from pbrezina at 2020-03-13 15:00:51
Metadata Update from @pbrezina:
Comment from pbrezina at 2020-04-14 13:40:21
Metadata Update from @pbrezina:
The text was updated successfully, but these errors were encountered: