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

Avoid registration of auth requirements for aliases and vanity paths

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

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Auth Core 1.5.0
    • Component/s: Authentication
    • Labels:
      None

      Description

      Right now when auth requirements are registered, they need to be registered for the resource path, as well as all vanity paths and potentially all combinations of aliases for that path. First of all, this creates potentially a lot of auth requirements for a single path, but as well requires that the registrar of the auth requirement to be aware of vanity paths and aliases and do the right thing and update the auth requirements whenever there are changes.
      We should avoid these additional registrations and processing.
      The SlingAuthenticator is currently checking the request path against the auth requirements. We could change this with checking the resolved path. So the authenticator could use a service user resolver and resolve the path and then check the auth requirements.
      This avoids all the extra work for the registrar of the auth requirements, but comes with the additional cost of a resolve call per request

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              cziegeler Carsten Ziegeler
              Reporter:
              cziegeler Carsten Ziegeler

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1.5h
                1.5h

                  Issue deployment