'Unrecognised user management configuration can not be upgraded' When Upgrading to Confluence 3.5 Due to User Management Configuration
When upgrading to Confluence 3.5, the upgrade fails.
The following appears in the
2011-03-21 15:22:44,510 ERROR [main] [atlassian.confluence.upgrade.UpgradeLauncherServletContextListener] contextInitialized Upgrade failed, application will not start: java.lang.UnsupportedOperationException: Unrecognised user management configuration can not be upgraded. com.atlassian.confluence.upgrade.UpgradeException: java.lang.UnsupportedOperationException: Unrecognised user management configuration can not be upgraded.
- Check your
atlassian-user.xmlfile. You should have a tag for osuser:
<osuser key="osuserRepository" name="OSUser Repository"/>
- Check the osuser.xml file. You'll have either a configuration to JIRA or directly to your LDAP server. Determine which one, then proceed to Causes and Resolutions below.
A deprecated form of osuser user management cannot be upgraded, and requires an intermediate step. There are currently two known causes for this error:
- Confluence is configured to use JIRA for User Management. To address this, see Upgrade to Confluence 3.5 with JIRA User Management Fails.
- Confluence is using osuser for "authentication only", as described in LDAP Authentication with OSUser. This has been deprecated, but has continued to work through Confluence 3.4. See Upgrade to Confluence 3.5 with OSUser LDAP authentication fails.
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.