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

permissions for screens that require the content list should have permissions that imply the correct permissions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.0-beta
    • Fix Version/s: 1.0-beta
    • Component/s: None
    • Labels:
      None

      Description

      Create a role with login, repository read and create. Login as that user, when you click add a new repo, the ui gets a 401 and turfs the user back out. This is because they also need the Repository Content permission. If you need that, then repository create should imply the content one too (and read for that matter)

        Attachments

          Activity

            People

            Assignee:
            cstamas Tamás Cservenák
            Reporter:
            brianf Brian Fox
            Last Updated By:
            Peter Lynch Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title