You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm reciving this error when testing user and group AD settings in crowd microsoft AD directory in the configuration page:
No results were found from your search. org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is java.naming.NamingException: [LDAP:error code 1 - 000004DC: LdapErr: DSID-0C09A5C comment.: In order to perform this operation a successful bind must be completed on the connection., data 0 v4563] remaining name 'OU Path listed'
The OU path for users and group in the message is correct. In the connect setting I'm able to connect to AD with no problems. I'm using Crowd 4.3.7
Guessing at possible options here - do you have a base DN set on the Connector tab, and then you're including the same value in the User/Group DN fields on the Configuration tab? The base DN is auto appended to the User/Group DN
Yes I am. I'm aware that it appends the base DN to the user and group DN. There is some verbiage under the text boxes that states that point. It appears this is a java issue. It does not seem to bind to AD. The URL for AD on the connector tab results in "The server address ad port are valid". So the connection to AD is good but java process will not bind to AD.
Do you have any other suggestions?
Hi @Mark Miller
I encountered the same error, I changed the connector configuration several times after which a successful connection was established, but synchronization didn't work correctly: No results were found from your search ... remaining name ...
It was with Crowd 4.3.7
After removing of created Directory -> reboot Crowd -> re-created a new directory = the problem is gone
As a guess, it could be some kind of logic related to caching on the Crowd side.