Method A - Permission per Repository
Some users choose to dedicate a full repository for anonymous access, this repository may be used to serve customer facing artifacts such as user manuals, patches/hotfixes and other public facing packages. To do this we will create a read only permission and add only the anonymous user.
Platform Configuration, User Management, Permissions, New Permission.
Give the permission an informative name, and add the resource (in this case - repository) that you wish to add to the permission by clicking “Add Repositories”, find the relevant repository,add it to “Selected Repositories”, and click “OK”
Once the resource is added, we will add the default “anonymous” user to the permission - Select “Users”, the “plus” sign, find the “anonymous” user, and add it to “Selected Users”.
The last step for this method is to select the actions the user will be able to perform for the selected resource, in our case we would like anonymous users to only have “Read” permission to this dedicated repository, therefore, we will check “Read”, and “Create”.
Method B - Permission per Repository with Include Patterns
In some cases, a more granular access is desired and you may want to allow the customers access to a specific path/directory inside a specific repository that holds the public artifacts, to do this we will add an include pattern to the same permission created in “Method A”.
Make sure to remove the default “**” include pattern prior to adding your own custom patterns.
In this example we added the following include pattern -
customer_documentation/manuals/2023.1/*.pdf
This pattern will allow the anonymous user access to all pdf files on this path, the same applies for UI view -