[Actions Center] Deprecated Service User Mapping Detected | Community
Skip to main content
V
ViaVu
Level 2
July 29, 2025
Question

[Actions Center] Deprecated Service User Mapping Detected

  • July 29, 2025
  • 3 replies
  • 798 views

Hi, To resolve "Deprecated Service User Mapping Detected", I created the following file under the osgiconf of the ui.config

"org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.cfg.json"

Following are its sample content. 

{

   "user.mapping": [
        "com.adobe.acs.acs-aem-commons-bundle:twitter-updater=[serviceuser--com.adobe.acs.acs-aem-commons-bundle--twitter-updater]",
         "aem-precompiled-scripts:scene7-asset-reader-service=[serviceuser--aem-precompiled-scripts--scene7-asset-reader-service]"
     ]
}
Does it look good to resolve the "Deprecated Service User Mapping Detected"? Or is there anything more to do?
 
 

3 replies

SantoshSai
Community Advisor
SantoshSaiCommunity Advisor
Community Advisor
July 29, 2025

Hi @viavu,

This looks good to me, except for one thing - the OSGi configuration filename you're using:

org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.cfg.json

To avoid the “Deprecated Service User Mapping Detected” warning and ensure the mapping is correctly registered, the filename should follow the pattern:

org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended~<name>.cfg.json

For example:

org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended~acs-commons.cfg.json

The ~<name> suffix is required to properly register the mapping as a named amendment configuration.

Other than that, your JSON structure and mappings look absolutely fine. Just make this filename adjustment, and you should be all set!

Also, worth to refer below articles since you just have posted sample code than actual code.

Santosh Sai
    V
    ViaVuAuthor
    Level 2
    July 29, 2025

    Hi @santoshsai, thank you for your quick response. 

     

    If I append the ~<name> suffix like the following...

    org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended~acsaemcommons.cfg.json

    I can see the file from CRX/DE interface. However, the same is not visible from the Server Config console. 

    If I name it as below...

    org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.cfg.json

    I can see it in both CRX/DE and also from Server Config.console

    The screenshot looks as seen below. Does this look correct and do you think this will help resolve the "Deprecated Service User Mapping" issue reported by AEM Cloud Services?

    SantoshSai
    Community Advisor
    SantoshSaiCommunity Advisor
    Community Advisor
    July 29, 2025

    @viavu 

    The user name must be enclosed in double quotes inside square brackets:

    "user.mapping": [
    "com.adobe.acs.acs-aem-commons-bundle:workflowpackagemanager-service=[\"serviceuser--com.adobe.acs.acs-aem-commons-bundle--workflowpackagemanager-service\"]",
    "com.adobe.acs.acs-aem-commons-bundle:twitter-updater=[\"serviceuser--com.adobe.acs.acs-aem-commons-bundle--twitter-updater\"]",
    "aem-precompiled-scripts:scene7-asset-reader-service=[\"serviceuser--aem-precompiled-scripts--scene7-asset-reader-service\"]",
    "com.adobe.acs.acs-aem-commons-bundle:package-replication-status-event-listener=[\"serviceuser--com.adobe.acs.acs-aem-commons-bundle--package-replication-status-event-listener\"]"
    ]
    Santosh Sai
      EstebanBustamante
      Community Advisor and Adobe Champion
      EstebanBustamanteCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      July 29, 2025

      Hi,

       

      The warning typically appears when an outdated pattern is used to create user mappings (the username was not enclosed in brackets). Your current configuration looks correct. For more details, please refer to the documentation here:
      https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/security/best-practices-for-sling-service-user-mapping-and-service-user-definition

       

      Hope this helps!

      Esteban Bustamante
        V
        ViaVuAuthor
        Level 2
        July 29, 2025

        Hi @estebanbustamante 

        Thanks for reviewing the configuration posted. 

        I did refer to the URL you have posted. The following suggested sample mapping provided in the document does not seem to be json compliant. I was not sure how to proceed with this approach and was not sure if this is applicable to the latest AEMaaCS environment.

        org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-my-mapping
        user.default=""
        user.mapping=[
        "com.adobe.cq.my-bundle:my-subservice\=[content-writer-service]",
        "com.adobe.cq.my-bundle:my-subservice-different-task\="[myfeature-configuration-writer-service,content-reader-service]"
        ]

        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        September 1, 2025

        @viavu just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

        Kautuk Sahni
        V
        ViaVuAuthor
        Level 2
        September 1, 2025

        Hi @kautuk_sahni No, this has not been resolved yet. The changes I tried as suggested did not work so far. As it appears, the issue is only reported for production and anything I try can be tested only on production. So, it is a slow process. If you have any suggestions to recreate the issue on lower environment and also any suggestions to resolve, that would be greatly appreciated. Thank you!

        Terms & ConditionsAccessibility statement

        Loading footer...