-
Notifications
You must be signed in to change notification settings - Fork 602
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
6.2.2-6.3.0 Alternative UPN Suffixes Problem #738
Comments
I don't think there is an issue with the alternate suffix - it will just try to connect and if no response - try the next domain in list. Have you removed some members or moved them from one group to another? |
No, I haven't removed member or edited the users. I even delete the ADBackend folder to allow it to generate it again but it still fails as you can see on the logs it only detect 3 user on version 6.3.0 but on version 6.2.1 it does detect all the users. |
I have noticed the same issue on my installation. I deviated from the original install instructions by creating a new IIS site with SSL enabled and a custom DNS name. It would be good to get it working again as AD management is awesome! |
I have 1 Alternative UPN Suffix on the Forest, till version 6.2.1 that was not a problem. But after the update i get this error and the user are not correctly populated.
Failed to create Directory context for domain "domain2.com".
System.DirectoryServices.ActiveDirectory.ActiveDirectoryObjectNotFoundException: The specified domain does not exist or cannot be contacted.
at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
at Bonobo.Git.Server.Helpers.ADHelper.GetDomain(String parsedDomainName)
For what i can see, it is trying to contact the domain suffix of the userPrincipalName, but because it is an alternative Suffiex it does not really exist as a domain inside the forest.
Im attaching the information i got from /home/diagnostics for 2.2.1 and the one after.
log bonobo 2-2-1.txt
log bonobo 3-0.txt
The text was updated successfully, but these errors were encountered: