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

SlingAuthenticator identifies wrong sibling node with AuthenticationInfo

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • Auth Core 1.3.18
    • Auth Core 1.3.26
    • Authentication
    • None

    Description

      Issue can be reproduced with the following steps:
      Create node "/page"
      Create sibling node "/page1"
      Define a protection handler for node: "/page"

      Expected:
      "/page" has AuthenticationInfo
      "/page1" does not have AuthenticationInfo (has anonymous)

      Actual: "/page" & "page1" are both having AuthenticationInfo

      Reason: SlingAuthenticator.java line 726: if (path.startsWith(holder.path)) Warning: The same check is used in 4 more places in code with similar behaviour.

      Attachments

        1. SLING-6053-patch.txt
          14 kB
          Antonio Sanso

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SLING-6563 Authentication Requirement: Siblings of Nodes with AuthRequired starting with same name result in 302

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SLING-4701 SlingAuthenticator.isAnonAllowed matches for all paths starting with the same characters

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #172

          Activity

            People

              asanso Antonio Sanso
              mkbrv Miklos Csere
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: