I have a production instance of JIRA v4.0.1 running on SunOS 5.10. I turned external password management off prior to doing a XML Backup but after I attempt a restore to v5.2.9 trying to upgrade our instance but it (both running on different servers and both standalone versions) fails with an error complaining about external password management being turned on. External passwork management was removed as a feature in v4.4. So, is there any way to force the import with the v4.0.1 data and keep JIRA from attempting to use external password management?
To clarify, have you copied the osuser.xml to the new JIRA directory before performing the upgrade? https://confluence.atlassian.com/display/JIRA/JIRA+4.3+Upgrade+Guide#JIRA4.3UpgradeGuide-ChangestousermanagementinJIRA
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
I am the product of AIM. I can hear that door swinging open and closed in my mind with absolute fidelity. I’d recognize that ding anywhere. At 15, as I typed away into AOL IM, I never imagined that ...
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!
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