6.5 AEM DAM Custom metadata schema not visible to all users | Community
Skip to main content
P
PovEim
Level 3
October 21, 2024
Solved

6.5 AEM DAM Custom metadata schema not visible to all users

  • October 21, 2024
  • 1 reply
  • 585 views

Hi Team,

 

Recently I created a custom metadata schema and applied it to a few folders within the DAM. It seems to be working as expected on my account and a few others. One thing I observed is that it is not visible to all the users within the same user group. I tested it with a new user and with a user who had been added to the DAM-Users group from a while back. I can confirm all user accounts (new and old) have the same access settings as they belong to the same user group. However, a few of them do not see the new metadata schema - they only see the default AEM DAM schema. At first I thought it may have been cookies related, so we cleared cookie history and also tested via incognito mode and via admin account impersonating the one that is glitching. No luck. Also, a lot of users lost access to the folder with the applied customised metadata schema - why is that?

Question - is there something else that needs to be done when applying a custom metadata schema onto the folders? What else should I look into to make sure all DAM users see the new metadata schema? 

 

Many thanks!

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 Anil_Chennapragada

hi @poveim ,

Hope you have already found the solution for the above. If not please try the below

  • Please check if the both the users (who have access and who do not to metadata schema) has the same user groups assigned.
  • Along with the DAM user group as mentioned above, if the users are also mapped to the different user group which explicitly denies access to the /conf folder this might happen. 
  • "deny" permissions always takes priority
  • Also please check the permissions for /conf folder for both the users who has access and who do not have access.

 

 

1 reply

A
Anil_ChennapragadaAccepted solution
Level 4
October 22, 2024

hi @poveim ,

Hope you have already found the solution for the above. If not please try the below

  • Please check if the both the users (who have access and who do not to metadata schema) has the same user groups assigned.
  • Along with the DAM user group as mentioned above, if the users are also mapped to the different user group which explicitly denies access to the /conf folder this might happen. 
  • "deny" permissions always takes priority
  • Also please check the permissions for /conf folder for both the users who has access and who do not have access.

 

 

    P
    PovEimAuthor
    Level 3
    October 22, 2024

    Hi @anil_chennapragada ,

     

    Thanks for your reply!

    I found the path where the metadata schema lives (/conf/global/settings/dam/adminui-extension/metadataschema/) - that's a win for me as none around knows this. I checked all user groups and their jcr:read permissions. None is denied, but I added the permission to "everyone" group and it seems that it works! I will have to run some tests still but it looks very promising! 

     

    Many thanks!

      Terms & ConditionsAccessibility statement

      Loading footer...