[
http://jira.codehaus.org/browse/MRM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135583#action_135583
]
Brett Porter commented on MRM-694:
----------------------------------
I'm having a problem using them with split authz.
Say the guest has perms to one repo and not the other, I get prompted for auth
on the group.
Likewise, if a user has perms to one repo and not the other, their auth fails
for the group with:
{code}
2008-05-21 14:17:24,210 [btpool0-5] INFO
org.apache.maven.archiva.security.ArchivaServletAuthenticator - Authorization
Denied [ip=0:0:0:0:0:0:0:1%0,
isWriteRequest=false,permission=archiva-read-repository,repo=testing] : no
matching permissions
{code}
I think that if the current user has access to *any* repo in the group they are
let in, and then what is shown is checked based on their permissions?
But if they have access to none, they are prompted.
> Virtual repositories or repository grouping
> -------------------------------------------
>
> Key: MRM-694
> URL: http://jira.codehaus.org/browse/MRM-694
> Project: Archiva
> Issue Type: New Feature
> Components: repository interface
> Reporter: Maria Odea Ching
> Assignee: Maria Odea Ching
> Fix For: 1.1
>
> Attachments: MRM-694-archiva-configuration.patch,
> MRM-694-archiva-webapp.patch, MRM-694-archiva-webdav.patch,
> MRM-694-web-interface.patch
>
>
> A number of managed repositories can be grouped together with that group
> having only one url. So you only need to specify that url in the settings.xml
> file and when Archiva receives a request via that url, it would look for that
> artifact from the repositories belonging to that group.
> More details are dicussed here:
> http://www.nabble.com/Archiva-1.1-Roadmap-td15262645.html#a15263879
--
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
