[
http://jira.codehaus.org/browse/MRM-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-579:
-----------------------------
Fix Version/s: (was: 1.x)
1.1
> Restricted access to remote repositories
> ----------------------------------------
>
> Key: MRM-579
> URL: http://jira.codehaus.org/browse/MRM-579
> Project: Archiva
> Issue Type: Wish
> Components: remote proxy, Users/Security
> Affects Versions: 1.0-beta-3
> Reporter: Arne Degenring
> Fix For: 1.1
>
>
> Originally discussed on
> http://www.nabble.com/Rights-management-for-Proxy-Connectors-tf4752902s177.html#a13590815
> It should be possible to configure Archiva in a way, that access to repo1
> through a proxy connector is available only for a few super users (=
> repository managers).
> In my scenario, normal users should only be able to access the artifacts
> available in the internal repository. In case they need a new artifact from
> repo1, they ask the repository manager to add it. The repository manager
> checks whether the artifact complies to e.g. company licensing rules, whether
> the metadata on repo1 is ok (which is mostly but not always the case), and so
> on. If everything is ok, he downloads the artifact including all
> dependencies. Afterwards the artifact should be available to everybody inside
> the company.
> Wendy Smoak and Brett Porter noticed that a permission on the remote
> repository probably would make most sense.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
