Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,299,666
Community Members
 
Community Events
165
Community Groups

Crowd Connector Microsoft AD User and Group configuration error

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

1 answer

0 votes

Hey Mark,

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

 

CCM

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.


Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
4.3.7
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

312 views 2 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you