Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

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

1 vote
JustinK Rising Star May 29, 2012

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

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!
JustinK Rising Star May 30, 2012

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.



0 votes
JustinK Rising Star May 29, 2012

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.



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events