Details

      Description

      REST API for permission lookup in the public PHP API
      Workshop notes: https://docs.google.com/document/d/10H8Z3kOKSJmovnfNVR-j8Z41jtrFoKQk3Qc0TqH0-ZA/edit#heading=h.jkrw4436749a

      Use case: Toggle UI elements depending on user permissions. What is needed is

      • PHP Repository API possibility to do reverse lookup on permissions: https://jira.ez.no/browse/EZP-26000
      • Extend REST to add permissions info in response, this should vary by user hash (this story)
      • Expose/use this info in REST client(s)
      • Use this info in UI to toggle buttons / actions

        Issue Links

          Activity

          Hide
          Gunnstein Lye added a comment -

          We want to fetch both the content and its permissions in one request, yes? Since we need to include the user hash we can't use the existing /content/objects/<ID>, but could use something like /content/objects/<ID>/permissions/<userhash>.

          Show
          Gunnstein Lye added a comment - We want to fetch both the content and its permissions in one request, yes? Since we need to include the user hash we can't use the existing /content/objects/<ID> , but could use something like /content/objects/<ID>/permissions/<userhash> .
          Hide
          André Rømcke added a comment -

          It needs to be a separate endpoint, maybe ala what you describe indeed, but be aware it will need location context if there is one to give proper reply for locations.

          There is a separate Epic assigned to Bertrand about embedding this and other things into content/location responses. So for this to work location and content info will need to have links on them that can be expanded by this feature (see specs for links between entities already there).

          Show
          André Rømcke added a comment - It needs to be a separate endpoint, maybe ala what you describe indeed, but be aware it will need location context if there is one to give proper reply for locations. There is a separate Epic assigned to Bertrand about embedding this and other things into content/location responses. So for this to work location and content info will need to have links on them that can be expanded by this feature (see specs for links between entities already there).
          Hide
          Gunnstein Lye added a comment -
          Show
          Gunnstein Lye added a comment - Spec work in progress: https://github.com/ezsystems/ezpublish-kernel/pull/1730

            People

            • Assignee:
              Gunnstein Lye
              Reporter:
              André Rømcke
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days, 1 hour, 20 minutes
                3d 1h 20m