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 am trying to create a custom directory connector in Crowd by implementing the interface RemoteDirectory. I have implemented necessary methods so far in order to test the custom directory from JIRA. I have added Crowd type of directory in JIRA. And when I test the remote directory from JIRA, it asks for credentials of a user in the remote directory for extended testing. And when I enter the credentials of a user existing in my custom directory (which is in a SQL Server database accessible via SOAP web service), Crowd calls certain methods of the Remote Directory interface (such as SearchUsers(), findUserByName(), searchGroupRelationships() and authenticate()). All these methods do return valid return values. However, the test results in JIRA shows authenticate step as failed, though it shows all the preceding steps as succeeded (as shown in the image attached). But I see in debug mode that the authenticate method of the RemoteDirectory implementation does return a valid User object (of type com.atlassian.crowd.model.user.User) with all its property values filled in.
Does anyone have any idea what may be the cause?
This issue is resolved. There was nothing wrong in implementation code. The problem was in Application configuration in Crowd. In the definition of Jira application in Crowd, Directories tab, the value in the column "Allow all to authenticate" for my custom directory was accidentally False. I had to changed it to true in order to resolve this issue.