Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-3462

Make ResourceAccessSecurity provider context and application context behave the same way

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      The problem was described and discussed in [1].

      GateResult.DONTCARE should be renamed to GateResult.CANTDECIDE to better reflect the intention of the returned value.

      Application context should behave like provider context and do not grant access if registered ResourceAccessGates only return GateResult.CANTDECIDE.

      This behavour should also be covered by some more integration tests.

      [1] http://markmail.org/message/dhvi5qa6573xhff6

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mykee Mike Müller
            mykee Mike Müller
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment