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

Your Points Tracker
  • 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
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?
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

Null Pointer Error when backing up Crowd

When I try to backup crowd to an xml file I get a null pointer error.

com.atlassian.crowd.migration.userMapper.addUserToXml (

I have check the database and there doesn't seem to be any null users, so why am I getting a null pointer error?

3 answers

The line in error is most likely:


Meaning that a user has a null credential, yes the code could be better, and it is a lot better in later releases of Crowd. So I would check to see if a user has a credential that is null.


There area bunch that are null. I have crowd set up to use LDAP as the authentication method. What should the credential be(I would guess "nopass" since that is what some of the others say)?

Would it be wrong to modify the null credentials in the database? Thanks for all the help

To help us verify the error could you let us know the version of Crowd you are using.

It would also help to have the complete stacktrace.



Sorry, I am running version 2.1.1 It is currently being run on a intranet only computer. To get the entire stack trace I would have to type it all out manually, is there a specific part you want to look at that I could get? Thanks!

I am assuming that you are using a delegated LDAP directory, so all auth will happen against LDAP and not against the local database.

Putting no 'nopass' into the credential column would be fine, since it will never be used for auth and that column expects an encrypted value, so nothing will every evaluate to 'nopass'.

You have actually hit which was fixed in 2.2.1 of Crowd.

As with any database change, I would recommend taking a backup of the database before doing this change.



Suggest an answer

Log in or Sign up to answer
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...

181 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