The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

com.atlassian.jira.util.dbc.Assertions$NullArgumentException: user should not be null!

Philip Colmer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 31, 2013

I've got an existing JIRA setup (with lots of users) and I've set up a Crowd server that is using LDAP as its primary directory.

On the Crowd server, I've defined the required jira-administrators, jira-developers and jira-users groups, all containing my LDAP account. I've configured an application for JIRA on Crowd and set it to use the LDAP directory and only allow members in the group. Testing authentication there works.

On JIRA, I've added Crowd as a directory and tested authentication there.

However, when I try to log in with my Crowd credentials, I get the error listed in the Question field. Logins with JIRA local accounts continue to work.

Regards

Philip

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
David Chan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 4, 2013

what version of JIRA are you running? It sounds like you may be running into a bug:

Take a look and see if that's it.

Philip Colmer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 10, 2013

We are using a version of JIRA that looks like it could be the bug that is the root cause. Unfortunately, we are going to have to build a new server rather than perform an in-place upgrade so it will take me a while to confirm this.

Nevertheless, marking this as the answer. Thank you!

TAGS
AUG Leaders

Atlassian Community Events