GitHub user ffslcschools added a comment to the discussion: LDAP troubleshooting
@ujan-shakya Ok, I finally have things back to working at the Domain level. Global Settings are clear of any specific data other than microsoftad and the associated ldap attributes. The ROOT domain has no settings, other than a search base dn so there isn't an error when clicking on the Add LDAP Account button. Otherwise, the settings are the same as above, I was able to point each domain to a different keystore to verify that they work although I am not 100 percent sure that it is utilizing them, I feel like the logs show that each look up tries all LDAP Configurations that are configured. @DaanHoogland I don't know if this is something that can be changed but it would seem to me that adding a ldap source in **Configuration / LDAP Configuration** should have the bind server, account and key store all configured there with a test button. Once that is there and verified to be working then associate the ldap source and search filters to the different domains, or if you only want one source the Global Configuration section. I am sure there is some design reason for the way it is setup, but it is not straight forward at all. GitHub link: https://github.com/apache/cloudstack/discussions/9899#discussioncomment-12376787 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
