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
Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot