Hi Team,
Ensure service user is working fine on our local instance but when we deployed the same config in AMS. Its throwing a error.. any input on this?
Caused by: org.apache.sling.api.resource.LoginException: Cannot derive user name for bundle com.adobe.acs.acs-aem-commons-bundle [613] and sub service ensure-service-user
Solved! Go to Solution.
Views
Replies
Total Likes
Make sure the system user is present on AMS, which you have created on your local and also make sure relevant permission are added to that system user on AMS.
Make sure the system user is present on AMS, which you have created on your local and also make sure relevant permission are added to that system user on AMS.
This error is thrown sometime when you only configure the bundleid and username(bundleid:username) in "Apache Sling Service User Mapper Service Amendment"
Configure the service mapping as following - bundleid:subServiceName=userName e.g. com.adobe.cq.sample.we.retail.core:testservice=testuser
Ensure the proper bundle is is configured
Regards
Albin I
Views
Replies
Total Likes
Can you perform a quick restart of the server? I would recommend using Ensure Service User from ACS Commons [0], it takes care of service user deployment with code package.
[0]: https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-service-users/index.html
Hey Sathya,
By the looks of it the instance is missing commons bundle.
Make sure you include acs-aem-commons package in your dependencies for your package.
Regards,
Peter
* Check for the existence of ensure-service-user on your AMS environment.
* Go to /system/console/configMgr, search for the service mapping for this bundle and ensure that the service user is included within [], and then save it.
Ex: I don't have acs bundle, but I have the following mapping configured for a service user.
com.adobe.cq.cq-experience-fragments:target=[targetservice]
Hope it helps !!
Views
Likes
Replies
Views
Likes
Replies