Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Authenticate step fails in custom directory connector testing (Crowd via JIRA)

Hello, 

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?  

Thanks!

RizwanCrowdTestViaJira.JPG

1 answer

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

180 views 6 7
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