Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-29071

Upgrade Failed due to Internal Directory is excluded from osuser.xml

    XMLWordPrintable

Details

    Description

      Summary of The Bug

      Upgrading JIRA failed during the user management migration with the following message thrown in atlassian-jira.log:

      2012-07-23 23:49:07,154 main INFO      [atlassian.jira.upgrade.UpgradeManagerImpl] ___ Performing Upgrade ____________________
      2012-07-23 23:49:09,212 main INFO      [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrate User Directory configuration
      2012-07-23 23:49:09,363 main INFO      [jira.upgrade.tasks.UpgradeTask_Build601] The following OSUser providers have been detected in the osuser.xml file.
      2012-07-23 23:49:09,363 main INFO      [jira.upgrade.tasks.UpgradeTask_Build601] com.opensymphony.user.provider.ldap.LDAPCredentialsProvider
      2012-07-23 23:49:09,363 main ERROR      [atlassian.jira.upgrade.UpgradeManagerImpl] Errors during Upgrade Task: Migrate User Directory configuration
      2012-07-23 23:49:09,364 main ERROR      [atlassian.jira.upgrade.UpgradeManagerImpl] Errors occurred during upgrade:
      2012-07-23 23:49:09,364 main ERROR      [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Error: JIRA is unable to migrate the User Directory configuration because the osuser.xml file does not contain a recognized configuration.<br/>Please see <a href="http://docs.atlassian.com/jira/docs-044/Upgrading+JIRA">Upgrading JIRA</a> for details.

      Cause of the Bug

      The cause of the bug is due to osuser.xml only contain external user management (eg: LDAP) configured on it and no internal repository configured.

      Example of problematic osuser.xml

      <opensymphony-user>
           <authenticatorclass="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://10.60.x.xxx:3268</property>
           <property name="searchBase">dc=xxxxxxxx,dc=internal</property>
           <property name="uidSearchName">cn</property>
           
           <property name="java.naming.security.principal">CN=xxx,dc=xxxxxxxx,dc=internal</property>
           <property name="java.naming.security.credentials">xxxxx</property>
           
           <property name="exclusive-access">true</property>
          </provider>
      </opensymphony-user>

      Workaround

      In order to workaround this bug, internal repository configuration needs to be added into the osuser.xml before re-try the upgrade process:

      
      <opensymphony-user>
           <authenticatorclass="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://10.60.x.xxx:3268</property>
           <property name="searchBase">dc=xxxxxxxx,dc=internal</property>
           <property name="uidSearchName">cn</property>
           
           <property name="java.naming.security.principal">CN=xxx,dc=xxxxxxxx,dc=internal</property>
           <property name="java.naming.security.credentials">xxxxx</property>
           
           <property name="exclusive-access">true</property>
          </provider>
      
          <provider class="com.atlassian.jira.user.osuser.JiraOFBizCredentialsProvider">
              <property name="exclusive-access">true</property>
          </provider>
       
          <provider class="com.atlassian.jira.user.osuser.JiraOFBizProfileProvider">
              <property name="exclusive-access">true</property>
          </provider>
       
          <provider class="com.atlassian.jira.user.osuser.JiraOFBizAccessProvider">
              <property name="exclusive-access">true</property>
          </provider>
      </opensymphony-user>

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              scahyadiputra Septa Cahyadiputra (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: