Upgrade ACS Common after version 6 throws error

[lax50]

Hi Team,

As we know Form API is deprecated from ACS common 6.0.0, In our project we used form API and we replaced with the ACS common Form custom classes instead directly refer acs common.

It is working fine in author and publisher with authentication, but it is not working for the anonymous user.

We debugged it and found the issue that service user "acs-commons-form-helper-service" removed from

bundle/src/main/java/com/adobe/acs/commons/users/impl/ProtectedAuthorizables.java

content/src/main/content/jcr_root/apps/acs-commons/config/org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-acs-commons.config

I have tried to add the same service user using below approach still got the same error 

org.apache.sling.api.resource.PersistenceException: Resource at '/content/test/jcr:content/par/canvas_2096355623/canvas_par/gridcolumn/1/start' is not modifiable.

https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-service-users/index.html

Is anyone face the similar kind of issue after upgrade latest acs common. 

[giuseppebag]

hi @lax50,

Are you certain that the issue is only related to the missing user? If so, have you tried using the Sling Repo Init scripts as suggested on the page https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-service-users/index.html?:

AEM 6.3 and greater should migrate to [Sling Repo Init scripts](https://sling.apache.org/documentation/bundles/repository-initialization.html) to ensure Authorizables and ACLS. Sling Repo Init supports creation of Users, Service Users and Groups, as well as the application of ACLs. It is generally recommended to prefer principal-based ACLs over resource-based ACLs when using Repo Init. 

[lax50]

I already tried above approach but still having the issue.