Provide option to manually migrate LDAP-local group memberships if there is no atlassian-user.xml during upgrade to 3.5

It's very easy to forget to copy over the atlassian-user.xml configuration file before upgrading to 3.5. If this happens, it is easy to configure the external directory after upgrading, but then local group memberships for external users are lost. There needs to be some way of recovering from this instead of having to rollback the migration and start again with atlassian-user.xml in place.

Workaround for 3.5

This improvement is available in Confluence 3.5.1, but can be used with 3.5. To do so:

1. Download the attached migratelocalgroups.jsp
2. Copy it to the confluence/admin folder in your Confluence instance
3. Start up Confluence and log in as a local user with administrator privileges
4. Visit http://your-instance.com/admin/migratelocalgroups.jsp
5. Follow the instructions on the page

select * from CWD_USER where id in (select child_user_id from CWD_MEMBERSHIP where parent_id = (select id from CWD_GROUP where group_name = 'confluence-administrators' and directory_id = (select id from cwd_directory where directory_type = 'INTERNAL')));