Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Issue: LDAP error 32 LDAP_NO_SUCH_OBJECT #1108

Closed
2 tasks done
cjohnston1158 opened this issue Sep 26, 2024 · 4 comments · Fixed by #1185
Closed
2 tasks done

Issue: LDAP error 32 LDAP_NO_SUCH_OBJECT #1108

cjohnston1158 opened this issue Sep 26, 2024 · 4 comments · Fixed by #1185
Labels
bug Something isn't working jira Import to Jira

Comments

@cjohnston1158
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues and found none that matched mine

Describe the issue

After configuring certificate auto-enrollment on Ubuntu 22.04 per the docs I am seeing LDAP error 32 LDAP_NO_SUCH_OBJECT. When trying to register with a Windows client, the Windows client was also not receiving the certificates.

There is another OU which was known to be working with a Windows client, so the GPO was compared. The new OU did not have the "Automatic Certificate Request Settings" configured, where the working OU did have this configured. The policy on the new OU was updated to match the working OU. Afterwards the Windows client was able to successfully download the certificates, however the Ubuntu client still is not.

Error message

Steps to reproduce it

https://documentation.ubuntu.com/adsys/en/stable/tutorial/certificates-autoenrolment/

Ubuntu users: System information

No response

Non Ubuntu users: System information

No response

Additional information

No response

Double check your logs

  • I have redacted any sensitive information from the logs
@cjohnston1158 cjohnston1158 added the bug Something isn't working label Sep 26, 2024
@didrocks
Copy link
Member

didrocks commented Sep 26, 2024 •
edited
Loading

FTR: requested information about Windows AD server and OS level. Also, can you run ubuntu-bug adsys and report the content there (see the bug template), so that we get all linux OS info, including its dependencies?

Some of the idea could be a stuck GPT.ini and no refresh for it.
Can you try to check for the cached policy on the windows client? You will have them under /var/cache/adsys. Please look at the GPOs directories, try to find the matching GPO with the object ID and check GPT.ini file content. The version (if the policy was correctly updated) should match the one on the AD server.

Thanks!

@cjohnston1158
Copy link
Contributor Author

DCs are running Windows Server 2019 or 2022.
2016 AD domain/forest Functional level.

@cjohnston1158
Copy link
Contributor Author

report.txt
policies

@denisonbarbosa denisonbarbosa added the jira Import to Jira label Oct 2, 2024
@manguera1
Copy link

Hi ,

Is there any update on this issue/bug ? I am having the same issue as cjohnston1158 .

Regards ,

Marco

@denisonbarbosa denisonbarbosa mentioned this issue Jan 31, 2025
Merged
denisonbarbosa added a commit that referenced this issue Feb 3, 2025
@denisonbarbosa
Certificate enrollment: Fixes for LDAP searches and for some issues w…
8726bfd 
…ith multiple domain environments (#1185)

This PR handles some issues encountered during certificate
auto-enrollment on environments with multiple domains. Specific details
for the fixes are listed on their respective commit messages, so I
highly recommend looking at those.

Closes #1108 
UDENG-4835
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working jira Import to Jira
Projects
None yet
Milestone
No milestone
4 participants
@didrocks @denisonbarbosa @cjohnston1158 @manguera1