/etc/dam/video/rep:policy breaks video component | Community
Skip to main content
JeremyJud
JeremyJud
New Participant
August 11, 2017
Solved

/etc/dam/video/rep:policy breaks video component

  • August 11, 2017
  • 1 reply
  • 879 views

AEM 6.2

The node /etc/dam/video/rep:policy breaks the request to http://<host>:<port>/etc/dam/video.profiles.list.json

500 Internal Server Error

java.lang.NullPointerException
at com.day.cq.dam.video.servlet.VideoProfileListServlet.getProfileName(VideoProfileListServlet.java:185)
at com.day.cq.dam.video.servlet.VideoProfileListServlet.writeVideoProfile(VideoProfileListServlet.java:124)
at com.day.cq.dam.video.servlet.VideoProfileListServlet.loopVideoProfiles(VideoProfileListServlet.java:114)
...

Because of that, the design dialog of the video component cannot be used, so the sources video profiles cannot be set and the video is not working.

How should I fix that? Where does rep:policy come from?

    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 liviu_chis

    I had this same issue Jeremy. I deleted the rep:policy node and it started working.

    The rep:policy node is what crx uses to track permissions on a given node. You'll see a series of allow and deny nodes underneath it that specify which users have and don't have access to it (ie the parent node of the given rep:policy node), and these are what the ACL's are composed of.

    It seems like the servlet that is used to generate a json list of video profiles is not aware that these kinds of nodes exist, and tries to process it as another profile and fails. It should instead filter and ignore them.

    While deleting the node is only a temporary solution, and not a very safe one because you might actually want to have certain users not be able to access the profiles node (which will require and recreate that rep:policy node), I don't know what else to suggest. Seems like Adobe will need to release a hotfix to fix the servlet.

    1 reply

    L
    liviu_chisAccepted solution
    New Participant
    August 17, 2017

    I had this same issue Jeremy. I deleted the rep:policy node and it started working.

    The rep:policy node is what crx uses to track permissions on a given node. You'll see a series of allow and deny nodes underneath it that specify which users have and don't have access to it (ie the parent node of the given rep:policy node), and these are what the ACL's are composed of.

    It seems like the servlet that is used to generate a json list of video profiles is not aware that these kinds of nodes exist, and tries to process it as another profile and fails. It should instead filter and ignore them.

    While deleting the node is only a temporary solution, and not a very safe one because you might actually want to have certain users not be able to access the profiles node (which will require and recreate that rep:policy node), I don't know what else to suggest. Seems like Adobe will need to release a hotfix to fix the servlet.

      Terms & ConditionsAccessibility statement

      Loading footer...