Unable to migrate user directory from 3.13 to 4.4

Hi,

I have the following error when trying to import data from Jira v3.13.5 in Jira v4.4.3:

JIRA Access Constraints

You cannot access JIRA at present.

<th width="40%">Description</th><th width="10%">Time</th><th>Level</th><th width="40%">Exception</th>
An error occurred performing JIRA upgrade task
2012-07-18 20:18:48 error
JIRA is unable to migrate the User Directory configuration because the osuser.xml file does not contain a recognised configuration.
Please see Upgrading JIRA for details.

In logs, I can see the following:

... /secure/SetupImport.jspa: Upgrade error JIRA is unable to migrate the User Directory configuration because the osuser.xml file does not contain a recognised configuration<br>Please see http://docs.atlassian.com/jira/docs-044/Upgrading+Jira for details.

My osuser.xml file contains the following:

<!-- osuser.xml autogenerated by user 'admin' on 24/juin/10 for JIRA 3.13.5
-->
<opensymphony-user>
<authenticator class="com.opensymphony.user.authenticator.SmartAuthenticator"/>

<provider class="com.opensymphony.user.provider.ldap.LDAPCredentialsProvider">
<property name="java.naming.factory.initial">com.sun.jndi.ldap.LdapCtxFactory</property>
<property name="java.naming.provider.url">ldap://myldap.mydomain.com:389</property>
<property name="searchBase">ou=People,dc=xxx,dc=com</property>
<property name="uidSearchName">uid</property>

<property name="java.naming.security.principal">uid=jirsystem,ou=people,dc=xxx,dc=com</property>
<property name="java.naming.security.credentials">xxx</property>

<property name="exclusive-access">true</property>
</provider>
</opensymphony-user>

Can somebody shed some light on it?

Thanks!

2 answers

1 accepted

This widget could not be displayed.

Please try with the following OSuser.xml

&lt;!-- osuser.xml autogenerated by user 'admin' on 24/juin/10 for JIRA 3.13.5
--&gt;
&lt;opensymphony-user&gt;
    &lt;authenticator class="com.opensymphony.user.authenticator.SmartAuthenticator"/&gt;
     
   &lt;provider class="com.opensymphony.user.provider.ldap.LDAPCredentialsProvider"&gt;
   &lt;property name="java.naming.factory.initial"&gt;com.sun.jndi.ldap.LdapCtxFactory&lt;/property&gt;
   &lt;property name="java.naming.provider.url"&gt;ldap://ctlqldap.xxx.com:389&lt;/property&gt;
   &lt;property name="searchBase"&gt;ou=People,dc=xxx,dc=com&lt;/property&gt;
   &lt;property name="uidSearchName"&gt;uid&lt;/property&gt;
    
     &lt;property name="java.naming.security.principal"&gt;uid=jirsystem,ou=people,dc=xxx,dc=com&lt;/property&gt;
     &lt;property name="java.naming.security.credentials"&gt;xxx&lt;/property&gt;
      
     &lt;property name="exclusive-access"&gt;true&lt;/property&gt;
    &lt;/provider&gt;
	&lt;provider class="com.atlassian.jira.user.osuser.JiraOFBizCredentialsProvider"&gt;
		&lt;property name="exclusive-access"&gt;true&lt;/property&gt;
	&lt;/provider&gt;

    &lt;provider class="com.atlassian.jira.user.osuser.JiraOFBizProfileProvider"&gt;
		&lt;property name="exclusive-access"&gt;true&lt;/property&gt;
	&lt;/provider&gt;

	&lt;provider class="com.atlassian.jira.user.osuser.JiraOFBizAccessProvider"&gt;
		&lt;property name="exclusive-access"&gt;true&lt;/property&gt;
	&lt;/provider&gt;
&lt;/opensymphony-user&gt;

Let me know how it goes.

Cheers,
Septa Cahyadiputra

My pleasure :).

Really great to hear that it finally worked on your end. It seems that the internal repositories need to included during the upgrade process.

Cheers,
Septa Cahyadiputra

It works!

So the right combination is to have Jira v4.4.4 and a osuser.xml that define several providers :)

Thank you!!

Hi there,

Just want to inform you that we have proceed to create a bug report here:

https://jira.atlassian.com/browse/JRA-29071

and update the previously given knowledge base to include your issue:

https://confluence.atlassian.com/display/JIRAKB/JIRA+Upgrade+Fails+due+to+osuser.xml+configuration

Cheers,
Septa Cahyadiputra

This widget could not be displayed.

Hi there,

Judging from your stack trace, it seems that you are encountering a known bug which is resolved in 4.4.4

https://jira.atlassian.com/browse/JRA-24161

However this bug root cause is due to multiple repositories configured on your OSuser.xml, which based on the provided osuser.xml content does not seems to be the case on your end.

Just for sanity check, could you please try to upgrade to 4.4.4 and see if the problem persist.

Hope it helps.

Cheers,
Septa Cahyadiputra

Hi,

thanks for your answer. I get the exact same message with 4.4.4.

Obviously, with the same osuser.xml as before

Hi there,

Sorry to hear that. Just to confirm again, may I know if you have multiple directories configured on your OSuser.xml

Unfortunately, no:

&lt;!-- osuser.xml autogenerated by user 'admin' on 24/juin/10 for JIRA 3.13.5
--&gt;
&lt;opensymphony-user&gt;
    &lt;authenticator class="com.opensymphony.user.authenticator.SmartAuthenticator"/&gt;
    
   &lt;provider class="com.opensymphony.user.provider.ldap.LDAPCredentialsProvider"&gt;
     &lt;property name="java.naming.factory.initial"&gt;com.sun.jndi.ldap.LdapCtxFactory&lt;/property&gt;
     &lt;property name="java.naming.provider.url"&gt;ldap://ctlqldap.xxx.com:389&lt;/property&gt;
     &lt;property name="searchBase"&gt;ou=People,dc=xxx,dc=com&lt;/property&gt;
     &lt;property name="uidSearchName"&gt;uid&lt;/property&gt;
     
     &lt;property name="java.naming.security.principal"&gt;uid=jirsystem,ou=people,dc=xxx,dc=com&lt;/property&gt;
     &lt;property name="java.naming.security.credentials"&gt;xxx&lt;/property&gt;
     
     &lt;property name="exclusive-access"&gt;true&lt;/property&gt;
    &lt;/provider&gt;
&lt;/opensymphony-user&gt;

Is it possible to run jira in a "more verbose" mode, ie to get more info in logs? Or to get the sources and debug it? Or anything else that may lead to a better understand on what is going on?

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in Statuspage

What are your best incident management tips and stories? #HugOps

 👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...

39 views 2 3
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