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 2008/10/17 16:43:20 UTC

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

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

Brett Porter updated MRM-812:
-----------------------------

    Fix Version/s:     (was: 1.2)
                   1.x

> artifact level security
> -----------------------
>
>                 Key: MRM-812
>                 URL: http://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
>             Fix For: 1.x
>
>
> 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.
-
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