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

After an upgrade from 4.2 to 5.2 (via 4.3) local users can no longer login

https://confluence.atlassian.com/display/JIRAKB/Local+Users+Can't+Log+in,+but+LDAP+Users+Can+after+Upgrade+to+v4.3

After upgrading to 5.2.6 from 4.2.3 local users can no longer login. The upgrade process was:

4.2.3 to 4.3.0

4.3.0 to 5.2.6

We are using mixed authentication with some users using LDAP authentication (staff) but the majority of of our clients and external users to our business use local accounts. After the upgrade some users can login but most can no longer log in at all. After researching the problem I can see that this was a known problem with the 4.3.0 upgrade, but now our main production Jira is offline for 100s of users.

As an emergency measure I have setup some users in active directory to allow logon (following Option 2: Add local users to LDAP in the knowledge base link above). But we have over 400 non-LDAP users who can no longer login. It is not feasible or desired to move these all to LDAP, but this option looks possible:

Option 3: Move the users directory via SQL

This is possible but difficult and risky

Note that if you were to do this then you need to restart JIRA in order to refresh the user caches.

We are running version 5.2.6 so how do we move the users directory in SQL?

Thanks for your help.

2 answers

1 accepted

0 votes
Answer accepted

In a perfect world a restore of the orginal Jira 4.2 and running through a different upgrade path would be great. If you can't because Jira is in a production environment and changes have been made after the upgrade you can always use this to update specific users to the internal database:

update cwd_user_attributes set directory_id=1 where user_id=(select id from cwd_user where user_name='username');

update cwd_user set directory_id=1 where user_name='username';

update cwd_membership set directory_id=1 where child_name='username';

This is where the internal directory has an id of 1, but check your directory id using the cwd_directory table first.

Hope this helps others.

Scott

1 vote
Ivan Maduro Atlassian Team Feb 18, 2013

Hi Scott,

Rather than moving user directories. I would suggest using a back up created prior to upgrading to restore your 4.2.3 installation. Once restored you can 4.3.1 from our download archive (which has the fix for this issue) and do your upgrade again as before.

Moving the User directories through SQL is trickier, but you will need to first check which directories have which IDs, you can find these in cwd_directory. note your Internal JIRA user directory.

Then you will need to change the directory_id fields in the cwd_user and cwd_user_attribute for all affected users. You will need to change it to the id you found in cwd_directory.

Like any major operation, please take a backup of your database before performing this operation.

Cheers,

Ivan.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Next-gen

Keyboard shortcuts have arrived for next-gen projects!

...ollected feedback from users around the lack of shortcuts, and we’re here to address that: In next-gen projects, I miss the keyboard shortcuts badly. This is particularly true on the Board, but also i...

102 views 0 1
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