JIRA upgrade : from 4.1.2 to 4.4.5, LDAP bypass needed


We are performing an upgrade for our client from JIRA 3.12 to 5.1.X.

We decided to go through 3.12 ->(a) 4.1.2 -> (b) 4.4.5 -> (c) 5.1.X

We managed to reach step (b) in TEST environment.

As we proceed the upgrade task from our location, we can't have access to the client's LDAP.

The osuser.xml file is correcty set in WEB-INF/classes folder.

The upgrade task from 3.12 to 4.1.2 succeeded. We can connect with any user whithout LDAP's connection.

In step (b), the upgrade task failed because it requires to connect to the client's LDAP.

Is there a way to bypass this LDAP connexion and to keep the group, user, role definition?

We thought about creating a internal admin user before doing the upgrade and then reconfigure a LDAP definition in the upgraded 4.4.5 JIRA. How about it?

How would Atlassian proceed to perform the data upgrade to JIRA 5.1.X without connecting to the client's LDAP directory?

Of course, when the upgrade procedure is tested and validated, we plan to deploy it in pre-production and then to the production with the client's LDAP.

For infos I already looked for solutions on the forum :



For the moment we restored the ORACLE dump before the upgrade to 4.4.5.

We thought about creating a local admin user before the migration,

then delete the osuser.xml in WEB-INF/classes

then perform the migration to 4.4.5

then depending on the environmnent

in Production reconfigure the LDAP server

in Test, perform the option 3 of the following page :


======> *Option 3: Move the users directory via SQL*

But there is no SQL provided. Could anyone help us with some clues please?

Thanks in advance

1 answer

1 accepted

Hi Johann,

As mentioned on the ticket, we highly not recommend you to do any SQL update directly on the database to migrate your users as it might leads to multiple issues down the line.

In regards to bypassing your LDAP server, I believe this would be possible only on your test environment since by bypassing the LDAP server JIRA won't be able to migrate its users successfully, and it would only carry over your "Internal Directory" users.

You could do this by adding administrative internal users before upgrading, and use a default {{osuser.xml}} (without LDAP connection) for your upgrade process.

Septa Cahyadiputra

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,774 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot