Hi, 

yes the user have permission to the release repository, because he´s 
Global Repository Manager as well as Global Repository Observer.
The user mentioned in archiva.log (having no permission) is the user doing 
the upload - it´s me and my own IP adress:-)

In the "User Management" view some users are not checked (überprüft) and 
some are locked (gesperrt) - why this?
Is there an SQL to check the database? Maybe something went wrong in the 
migration phase?

Thanx, Torsten




Brett Porter <br...@apache.org> 
Gesendet von: Brett Porter <br...@porterclan.net>
11.08.2010 07:20
Bitte antworten an
users@archiva.apache.org


An
users@archiva.apache.org
Kopie

Thema
Re: Authorization Denied (return code 401) at mvn:deploy after migration 
from 1.1.3 to 1.3.1






It should migrate fine, unless you ended up losing the users database.

When you view the user in the UI, do they have manager permission to the 
release repository?

Are you use that user is being used to do the upload (you can see in the 
request log).

- Brett

On 11/08/2010, at 12:23 AM, torsten.reinh...@gi-de.com wrote:

> Hi, 
> 
> we have some users in archiva having Repository Manager and Repository 
> Observer roles to the release- and snapshot repository.
> 
> With Archiva 1.1.3 these users could deploy artifacts - after migration 
to 
> 1.3.1 they could not any more !
> 
> [INFO] Error deploying artifact: Failed to transfer file: 
> http://[server].intern:8080/archiva/repository/snapshots/.......jar. 
> Return code is: 401
> 
> In archiva.log I read the following lines:
> 
> 2010-08-10 16:03:21,321 [http-8080-5] INFO 
> org.apache.maven.archiva.security.ArchivaServletAuthenticator  - 
> Authorization Denied 
> [ip=xx.x.xx.xxx,permission=archiva-upload-repository,repo=snapshots] : 
no 
> matching permissions
> 2010-08-10 16:03:21,368 [http-8080-5] INFO 
> org.apache.maven.archiva.security.ArchivaServletAuthenticator  - 
> Authorization Denied 
> [ip=xx.x.xx.xxx,permission=archiva-upload-repository,repo=snapshots] : 
no 
> matching permissions
> 
> Dropping and recreating the user is maybe a workaround - but what is the 

> reason ?
> Is there any additional step to do, when updating ?
> 
> Thanx, Torsten

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





Reply via email to