archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lothar Werzinger <>
Subject Re: Custom roles for Archiva repository access
Date Wed, 29 May 2013 16:13:30 GMT
Response inline.

On Wed, May 29, 2013 at 2:49 AM, Olivier Lamy <> wrote:

> 2013/5/29 Lothar Werzinger <>:
> > Hi,
> >
> > I am researching Archiva and I tried using the REST API for Archiva 1.4.
> >
> > I am using 1.4-M3 as well as the staged 1.4-M4 from
> >
> >
> >
> > Is it possible to create new custom roles for Archiva repository access?
> > I could not find a way to create new roles, but I might have missed it.
> >
> No
> > I would like to grant a certain group of users the right to upload new
> > artifacts, but I don't want them to have the repository manager role for
> > the repository in question, as that allows e.g. deletion of artifacts as
> > well.
> No that's not possible currently.
> Roles (like Foo Repository Manager) are created from template roles
> (Repository Manager)
> The goal could be to create a new Role with only the operation
> "archiva-upload-repository".
> But that's not exposed as a REST service.
> Create a issue. If you have a bit of time that's something to in
> redback-core.

I'd love to, but when I go to there's
no way for me to register for a login. The message says
*Not a member? To request an account, please contact your JIRA

> --
> Olivier Lamy
> Ecetera:
> |


Lothar Werzinger

Principal Architect

Tradescape, Inc. - Enabling Efficient Digital Marketplaces

+1-650-931-6719 (direct)

+1-800-697-6068 (main) Ext. 116


This message and any attachment (the "message") is intended solely for the 
addressees and is confidential. If you receive this message by mistake, 
please delete it and notify the sender immediately. Any use not 
in accordance with its purpose, any out-spread or disclosure, either as a 
whole or partially, is prohibited except with formal approval. Internet 
cannot guarantee the integrity of this message, therefore Tradescape will 
not be liable for the message if modified.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message