Did you retain your user's database in the upgrade? It seems that you have not granted permissions to the release repository to the user that is attempting to do the deployment.
Cheers, Brett 2008/9/27 solo1970 <[EMAIL PROTECTED]>: > > Hello, > > I am new to this list and the whole Archiva world, so please be patient... > > We've recently upgraded to Archiva 1.1.2 and we are now getting the > following error when trying to deploy using Maven to the Archiva repository: > > ... > [INFO] [deploy:deploy] > altDeploymentRepository = > release::default::dav:http://maven.xxxx.se:8888/repository/release > [INFO] Using alternate deployment repository > release::default::dav:http://maven.xxxx.se:8888/repository/release > Uploading: > http://maven.xxxx.se:8888/repository/release/com/xxxx/riot/riot-parent/3.0.0-R2A01/riot-parent-3.0.0-R2A01.pom > Sep 26, 2008 10:30:52 AM org.apache.commons.httpclient.HttpMethodBase > processAuthenticationResponse > INFO: Already tried to authenticate with 'Repository Archiva Managed > Repository' authentication realm at maven.xxxx.se, but still receiving: > HTTP/1.1 401 Unauthorized > Sep 26, 2008 10:30:52 AM org.apache.commons.httpclient.HttpMethodBase > processAuthenticationResponse > INFO: Already tried to authenticate with 'Repository Archiva Managed release > Repository' authentication realm at maven.xxxx.se, but still receiving: > HTTP/1.1 401 Unauthorized > ... > > Thanks! > > solo > -- > View this message in context: > http://www.nabble.com/Failed-authentication---archiva-1.1.2-tp19692615p19692615.html > Sent from the archiva-users mailing list archive at Nabble.com. > > -- Brett Porter Blog: http://blogs.exist.com/bporter/
