Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-5621

Blocking routing rule omits "applied mappings"

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5
    • Component/s: None
    • Labels:
      None

      Description

      Hence, it wrongfully does not reveal what mapping causes it's denial.

      For example, start nexus and

      • create INCLUSIVE routing rule ^/log4j.*, applied to ALL groups, and make Central included
      • enter this into browser: http://localhost:8081/nexus/content/groups/public/log4j/log4j/1.2.13/log4j-1.2.13.pom?describe
      • inspect response, especially fields appliedMappings (should contain the newly created rule from above) and processedRepositoriesList (should contain public and central only).
      • now change the rule you created above from INCLUSIVE to BLOCKING.
      • repeat the describe request from above.

      It describes 404 okay (as you just blocked the log4j from public), but the describe says NOTHING about appliedMappings, which is wrong.

        Attachments

          Activity

            People

            Assignee:
            bhanzelmann Benjamin Hanzelmann
            Reporter:
            cstamas Tamás Cservenák
            Last Updated By:
            Peter Lynch Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                tigCommentSecurity.panel-title