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: 

Reactivate inactive Jira user - LDAP

Joe Mallon
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.
October 12, 2013

We're trying Jira 6.1 with LDAP authentication. We previuosly used 5.2 with LDAP. In 6.1, an inactive LDAP user is rendered inactive in Jira. This is not true in 5.2.

Since we're trying to migrate a bunch of old defects from another system into Jira, we need to assign defects to those inactive users. Is there a way to temporarily reactive them?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
EddieW
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.
October 12, 2013

As long as you have marked a LDAP group shared by those users in the global permissions (and permissions schemes to grant the "assignable user" permission they should be seen as active. Maybe I just need more details on what you mean by inactive.

Joe Mallon
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.
October 13, 2013

The user no longer works at our company, and so is marked with access control 514 in Active Directory. The user is then marked "inactive" in Jira - see attached screen shot.

The person working on migration says:

More testing reveals that you can force the Web Gui to assign an inactive user, we just can’t get the command line to. Both rest client and sli interface return an error if you try to assign an inactive user to a bug.
We cannot upgrade to version 6 unless this is resolved.