Simplify upgrades with Active Directory and a custom username attribute

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 3.5.11
    • Affects Version/s: None
    • Component/s: None
    • None

      Currently, if confluence is used with Active Directory and the username is not sAMAccountName, the automated upgrade will fail to detect that the LDAP server is AD, and could then trigger exceptions due to using the wrong page size when retrieving records, which then causes the upgrade to fail. To work around this, administrators are forced to jump through several hoops to get a working upgraded system (at its simplest: upgrade without atlassian-user.xml, drop atlassian-user.xml into position, log in as admin, manually add Active Directory in User Directories UI, run migratelocalgroups.jsp). We need to simplify this process so that administrators never have to recreate their AD configuration in Confluence or need to run manual upgrade steps.

              Assignee:
              Richard Atkins
              Reporter:
              Richard Atkins
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: