User Roles and permission is not getting reflected through acl (.yaml) | Community
Skip to main content
L
lone_Ranger
Level 4
July 13, 2023

User Roles and permission is not getting reflected through acl (.yaml)

  • July 13, 2023
  • 2 replies
  • 1393 views

Hi @16227148

 

I have a requirement to deny delete for some user on Experience fragment.

 

Initially i have denied 

/content/experience-fragments/project_name/xxxx/xxxx/xxxx/ 

ex - 

- local-ex-authors:
    - path: /content/experience-fragments/project_name/xxxx
      permission: deny
      actions: create,modify,delete,replicate
 
and in other file i have allowed permission ex - 
 
    - path: /content/experience-fragments/project_name/xxxx/xxxx/xxx/en_ae
      permission: allow
      actions: read,modify,create,replicate
      privileges: jcr:addChildNodes,jcr:modifyProperties,jcr:removeChildNodes
 

Applied modify to parent but child is not getting checkbox checked.

 

Thanks for help!!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
July 13, 2023

Hello @lone_ranger 

 

Please verify following:

- if the file was processed by visiting Security > Netcentric ACL Tool UI

- Are there any errors reported?

- You should use only spaces in the yaml file. Tabs is not supported. If tabs are found, try deploying again after making the corrections.

Aanchal Sikka
    L
    lone_RangerAuthor
    Level 4
    July 13, 2023

    Hi  @aanchal-sikka ,

    No there is no error

      Sudheer_Sundalam
      Community Advisor
      Sudheer_SundalamCommunity Advisor
      Community Advisor
      July 13, 2023

      @lone_ranger ,

      Also, it is worth to double check the runmode configuration naming conventions.

      Check the runmode of the server (http://localhost:4502/system/console/status-slingsettings) you are trying invoke Netcentric ACL Tool UI is exactly matching with the naming convention of .yaml file.

      author.dev, author.qa, author.stage, author.prod etc.,

        Tanika02
        Tanika02
        Level 7
        July 14, 2023

        Hello @lone_ranger -

         

        • Verify if the child node has its own ACL (Access Control List) defined that could be overriding the inherited permissions from the parent node.
        • If the child node has its own ACL and the "modify" permission is not inherited, you can explicitly grant the "modify" permission to the child node.
          L
          lone_RangerAuthor
          Level 4
          July 14, 2023

          Hi @tanika02 ,
          Child node are XF and also no permission is overwriting it.

           

          Thanks

            aanchal-sikka
            Community Advisor
            aanchal-sikkaCommunity Advisor
            Community Advisor
            July 14, 2023

            @lone_ranger 

             

            Verify often, when there are no errors, but permissions are not applied, its the file formatting thats an issue.

             

            Can you please assure that you are using only spaces in the yaml file? 

            Aanchal Sikka
              Terms & ConditionsAccessibility statement

              Loading footer...