I would like to put Proximity into corporate use. While anyone can download artifacts from Proximity, only a few people can do deploy.
I would like to setup the AffirmativeAccessManager to use ComplexPropertiesFileUsernameBasedAccessDecisionVoter. However, I get return code 500, when I do “deploy:deploy-file! I added some debug codes and found the “request.username” from the Voter was “null”. I did add a “server” entry with username and password in setting.xml and specify it in –DrepositoryId when I did “deploy:deploy-file”, like: mvn deploy:deploy-file -DrepositoryId=xxxx -Durl=http://yyyy …. After reading the follow mail http://www.nabble.com/Re%3A-Proximity-with-https-client-certs-tf1711334s177.html#a4646452 I guess using https is a MUST? -- View this message in context: http://www.nabble.com/Proximity-into-corporate-use-tf4848068s177.html#a13871104 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
