User/Group Migration issues | Community
Skip to main content
Level 5
April 8, 2022
Solved

User/Group Migration issues

  • April 8, 2022
  • 1 reply
  • 1962 views

Hi All,

 

We are trying to migrate users/groups from AEM 6.0 to AEM 6.5, with the goal of all the permissions and privileges retained. I am following this documentation, https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16448.html?lang=es-ES. After the migrations, all the original permissions are gone.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by JeevanRaj

I almost did the same thing as you did. With an exception that the "Package ACL handling" is "overwrite". Also another question, do we have to put all the users in the "Principle names"? I wonder what if we have a few hundred or even thousands?


If you are going to migrate the users/groups using ACLS then you will have to put those users/groups under "Principle names". If you have a large number of users, those users must be part of a few groups. You can provide these groups name instead of users under "Principle name".

Anyway in your case you have already migrated the users as per the adobe document, right? Unselect "Include principles" and try getting the acls of couple of users. If this doesn't work there might be some issue with acs commons version you are using which we can look into further.

1 reply

Kevin_GTaAuthor
Level 5
April 8, 2022

JeevanRaj
Community Advisor
Community Advisor
April 8, 2022

Hi @kevin_gta 

 

ACL packager pretty much does the job. I had used this to migrate users, groups and their acls from 6.2 to 6.5 and it worked flawlessly.

 

I see that you are migrating acls under /content. Is it possible that you have installed acls package first and then installed/reinstalled content package? I suspect this might be one of the reason its not showing up.

 

Regards,

Jeevan

Kevin_GTaAuthor
Level 5
April 8, 2022

Interesting. I actually tried it as you said before the content migration a while ago, it failed also. But the failure didn't come from the ACL migration, but because we never reached the ACL migration due to AEM 6.0 has a very strict rule against ACS-Commons. Now we got a version (2.12.0) that works for AEM 6.0, but never tried the ACL migration before the content migration since then. You got a very good point. Thanks for your suggestion.