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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When I try to backup crowd to an xml file I get a null pointer error.
com.atlassian.crowd.migration.userMapper.addUserToXml (userMapper.java:87)
I have check the database and there doesn't seem to be any null users, so why am I getting a null pointer error?
The line in error is most likely:
userElement.addElement(USER_XML_CREDENTIAL).addText(user.getCredential().getCredential());
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.
Justin,
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 https://jira.atlassian.com/browse/CWD-2284 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.
Cheers,
Justin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
Cheers,
Justin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.