Maven Wagon
  1. Maven Wagon
  2. WAGON-116

Proxy authentication not authenticating with settings

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.1
    • Component/s: wagon-http
    • Labels:
      None
    • Environment:
      Linux with BlueCoat firewall/proxy
    • Number of attachments :
      1

      Description

      On a windows machine, authenticated on an NT domain, the proxy username and password appear to be sufficient for getting the lightweight http wagon to download artifacts.

      On a linux machine, which is connected to the domain's network but not authenticated on the domain, the same settings do not work.

      To further compound the confusion of the situation,
      setting http_proxy with the specified username and password using

      export http_proxy=http://USERNAME:PASSWORD@PROXYIP:PROXYPORT

      allows me to use wget on an artifact's URL and retrieve it from the command line, indicating an issue with the proxy settings for java (since a compiled app from the command line successfully navigates the proxy).

      There appears to be no additional logging available.

      Attached is the output of mvn -X that shows the trace.

      Currently checking out the trunk sources to attempt further debugging.

        Activity

        Hide
        Brett Porter added a comment -

        I think you need additional ntlm system properties that the lightweight provider doesn't set for you

        Show
        Brett Porter added a comment - I think you need additional ntlm system properties that the lightweight provider doesn't set for you
        Hide
        Tim Scott added a comment -

        We're having a similar problem with a proxy server requiring the setting of http_proxy as an environment variable. Is this not a way to encode the NT domain into the value?
        eg:
        http://DOMAIN%5CUSERNAME:PASSWORD@PROXYIP:PROXYPORT
        or:
        http://USERNAME%40FQDN:PASSWORD@PROXYIP:PROXYPORT

        Show
        Tim Scott added a comment - We're having a similar problem with a proxy server requiring the setting of http_proxy as an environment variable. Is this not a way to encode the NT domain into the value? eg: http://DOMAIN%5CUSERNAME:PASSWORD@PROXYIP:PROXYPORT or: http://USERNAME%40FQDN:PASSWORD@PROXYIP:PROXYPORT
        Hide
        Mykel Alvis added a comment -

        Yes. The USERNAME in the above example required that.
        You can also do it by
        export HTTP_PROXY='http://DOMAIN\USER:PW@proxy:PORT'
        or export HTTP_PROXY="http://DOMAIN
        USER:PW@proxy:PORT"

        First one appears more generic across shells (except for "export", of course)

        It would maybe be nice if there were a parameter to set for this in the provider, rather than having to juggle escaped backslashes for windows, but that's just an idea.

        Show
        Mykel Alvis added a comment - Yes. The USERNAME in the above example required that. You can also do it by export HTTP_PROXY='http://DOMAIN\USER:PW@proxy:PORT' or export HTTP_PROXY="http://DOMAIN USER:PW@proxy:PORT" First one appears more generic across shells (except for "export", of course) It would maybe be nice if there were a parameter to set for this in the provider, rather than having to juggle escaped backslashes for windows, but that's just an idea.

          People

          • Assignee:
            Unassigned
            Reporter:
            Mykel Alvis
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: