Hello,
I have setup something quite similar for my former company, although
the physical security requirements were less stringent: We had
off-shore developers, customer-side developers and our own developers
located both at our main office and customer's office. We needed to
isolate each
I have a requirement to prevent external access to a repository without
authorization.
Does the username/password in the servers section of settings.xml work with
Basic Auth?
Are there other authentication methods that can be utilized?
The situation is this:
- The company is primarily a MS
authorized_keys is the only way I know to do this easily. Look into the
webdav wagon. That might allow you to use your LDAP auth for HTTP PUTs and
GETs to/from the repo so you don't have to go through any Unix security
hurdles.
[EMAIL PROTECTED] wrote on 08/16/2006 12:36:45 PM:
I'm not a
Thanks. I'll look into the WebDAV support.
On 8/16/06, Mike Perham [EMAIL PROTECTED] wrote:
authorized_keys is the only way I know to do this easily. Look into the
webdav wagon. That might allow you to use your LDAP auth for HTTP PUTs
and
GETs to/from the repo so you don't have to go