Browse storage doesn't work for users with restricted read access.

Problem: 

You've restricted read access to a repository by using a repository target with a regular expression that matches a group ID, such as "/com/mycompany/team-a/.*".  This works, but now users with this privilege can't use the "Browse Storage" tab in the UI.

Solution:

This is happening because the folders "/", "/com", etc. do not match your regular expressions.

To fix this you also need to grant read access to the paths in the tree, so use a regular expression like this one:

 /|/com/|/com/mycompany/|/com/mycompany/team-a/.* 

Alternatively, you can grant access to all directory listings regardless of where they are in the hierarchy:

.*/

This will grant access to all directory listings, but will not grant any access to artifacts within a directory.

Have more questions? Submit a request

2 Comments

  • 0
    Avatar
    Bill Buie

    A funny thing-- I was sure this missed the root cause of my problem, and I carefully constructed a test case to prove it.  And then in the process I discovered that my regular expression had left out the leading slash (/)!

  • 0
    Avatar
    Peter Lynch

    We are closing this article for comments.

    If you have a support license, please contact us by submitting a support ticket.

    If you do not have a support license, please use our Nexus Users List or our other free support resources.

Article is closed for comments.
Powered by Zendesk