Cannot Establish Secured Connection to Enterprise Maven Repository

[wayn23]

I am using ServiceMix-4.4.0-fuse-00-27 and trying to establish a connection to a LAN attached local enterprise Archiva server over an https connection.

I am following the information described in http://ops4j1.jira.com/wiki/display/paxurl/Mvn+Protocol

I have added the following entries to the org.ops4j.pax.url.mvn.cfg file.

org.ops4j.pax.url.mvn.settings=file:${user.dir}/config/maven-settings.xml

org.ops4j.pax.url.mvn.repositories=https://internal.server.com:8443/archiva/repository

In the ${user.dir}/config/ directory I added the file maven-settings.xml with contents

  ...

The connection never works.  Here is a sample from the log

12:05:18,474 DEBUG org.ops4j.pax.url.mvn          1.2.6            Collecting versions from repository https://internal.server.com:8443/archiva/repository/corporate/,releases=true,snapshots=false | Logger(org.ops4j.pax.url.mvn.internal.Connection) Thread(Thread-22)

12:05:18,552 DEBUG org.ops4j.pax.url.mvn          1.2.6               Could not download [Version from URL https://internal.server.com:8443/archiva/repository/corporate/corp/RuntimeModel/1.0.0/RuntimeModel-1.0.0.jar] | Logger(org.ops4j.pax.url.mvn.internal.Connection) Thread(Thread-22)

The file does exist and if I use the url in my browser, I can retreive the file successfully. 

What I am trying to accomplish is a secure connection to archiva. I would like to use the encrypted password approach as described in http://maven.apache.org/guides/mini/guide-encryption.html

[ffang]

Hi,

Try  change

org.ops4j.pax.url.mvn.repositories=https://internal.server.com:8443/archiva/repository

to

org.ops4j.pax.url.mvn.repositories=https://userid1:[e-mail]:8443/archiva/[e-mail]:8443/archiva/repository

Freeman

[wayn23]

I tried the http://userid:password@ option, but it means that the password does not contain any special characters, like ?@ and mine does. 

Can the password be stored in the settings.xml file?  Can it be encrypted?

[wayn23]

I just want to follow up on how I solved this.

There is a bug in m2eclipse https://bugs.eclipse.org/bugs/show_bug.cgi?id=343009 that fails to respond to a challenge response for authentication from a proxy if the challenge is for an NTLM account. A work-around is to put something between m2eclipse and the proxy that knows how to handle the challenge properly.  CNTLM is an open source proxy to proxies.  The way it helps is it is setup to provide the NTLM credentials to the company proxy when it asks.  m2eclipse is then configured to use the CNTLM proxy.  (CNTLM will only accept requests from the local machine, so the credentials cannot be used externally.)

At runtime, m2eclipse calls the CNTLM proxy, which then calls the company proxy.  The company proxy challenges for credentials and the CNTLM proxy provides them and the call completes normally.

[ffang]

Hi,

Thanks so much for sharing your solution.

Freeman