Here is the use case: With Archiva 2.1, they've added a "Delete Artifact" possibility in the UI, as long as you are a "Repository Manager", you have access to it. In the past, we used the "guest" logon for everyone which was "Repository manager" for our snapshots and development repositories, hence no username/password in the settings.xml file. Ande everyone can deploy.
Now we don't want everyone to go to the UI and have the possibility to delete artifacts from those repositories, so we can't give "guest" the "Repository manager" role for those repositories. We've then created a "deployment" user which has those roles, but we need to encrypt the password so that not everyone can login to the UI, but can deploy from the command-line to those repositories. Does it make sense? Sonia Wayne Fay wrote: > >> is there something similar for the settings-security.xml file????? It's >> impossible to manage everyone having a settings-security.xml file in >> their >> home directory..... > > If everyone is sharing all the settings etc, then why are you > concerned about encrypting passwords?? What's the use case? > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/Question-concerning-settings-security.xml-location-tp22932257p22935376.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
