You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2011/09/12 16:41:07 UTC

[jira] Closed: (MRM-812) artifact level security

     [ https://jira.codehaus.org/browse/MRM-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRM-812.
----------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: Backlog)

> artifact level security
> -----------------------
>
>                 Key: MRM-812
>                 URL: https://jira.codehaus.org/browse/MRM-812
>             Project: Archiva
>          Issue Type: New Feature
>          Components: Users/Security
>    Affects Versions: 1.0.2
>         Environment: Linux
>            Reporter: Franck HUGOT
>
> I would like to know if it is possible to manage access control to a specific path of repository .
> Example: user "A" will access to only org/maven/apache/* of a repository but this path will be forbidden for user B.
> I think white list and black list will be for all users. 
> Do you have an idea of how can I do that? 
> If I create a specific repository to user "A", I will duplicate the artifacts. I don't think it's a good solution.
> I guess it would be possible with an Apache in front of Archiva but I would prefer to manage this in the application.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira