Solved! Go to Solution.
Views
Replies
Total Likes
Thank you all now it's working. There was a mistake in the symbolic name i have given.
Hello @Keerthi987
I guess you are missing the config for
org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl. Please follow the link to configure Service User. You would also need to update the API
https://medium.com/@toimrank/aem-service-user-mapping-and-resourceresolver-bd4a15d8cff2
no I mapped service user. does default workspace points to 4502?
I have been using getServiceResourceResolver for a long time.
The loginService() is creating issue after upgrade everywhere? Or in a specific case only?
Have you correctly written the config file for SysytemUserMysite?
In your org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-my-project.config file
# Configuration created by Apache Sling JCR Installer
service.ranking=I"100"
user.mapping=["com.my-project:SystemUserMysite\=your-service-user-name"]
See this documentation: https://aemhints.com/2020/11/08/service-users-mapper-aem/
yes
Then please share the exception message
Hello @Keerthi987 ,
Please make sure you correctly referenced this.
user.mapping=["SymbolicNameFromBundle:SystemUserMysite\=your-service-user-name"]
Go to the http://localhost:4502/system/console/bundles
Search for your bundle and get the Symbolic Name
Otherwise, there should not be any issue if you correctly create the service user.
Thank you all now it's working. There was a mistake in the symbolic name i have given.
Do you have the System User available in the given environment/AEM Local wherever you are executing this?
yes it is.
Views
Likes
Replies