You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mykel Alvis (JIRA)" <ji...@codehaus.org> on 2006/12/13 23:58:40 UTC

[jira] Created: (WAGONHTTP-14) Proxy authentication not

Proxy authentication not 
-------------------------

                 Key: WAGONHTTP-14
                 URL: http://jira.codehaus.org/browse/WAGONHTTP-14
             Project: wagon-http
          Issue Type: Bug
    Affects Versions: 1.0-beta-1, 1.0-alpha-6
         Environment: Linux with BlueCoat firewall/proxy
            Reporter: Mykel Alvis
         Attachments: myfile.txt

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.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (WAGONHTTP-14) Proxy authentication not authenticating with settings

Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/WAGONHTTP-14?page=all ]

Wendy Smoak updated WAGONHTTP-14:
---------------------------------

    Summary: Proxy authentication not authenticating with settings  (was: Proxy authentication not )

> Proxy authentication not authenticating with settings
> -----------------------------------------------------
>
>                 Key: WAGONHTTP-14
>                 URL: http://jira.codehaus.org/browse/WAGONHTTP-14
>             Project: wagon-http
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-6, 1.0-beta-1
>         Environment: Linux with BlueCoat firewall/proxy
>            Reporter: Mykel Alvis
>         Attachments: myfile.txt
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (WAGON-116) Proxy authentication not authenticating with settings

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/WAGON-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated WAGON-116:
-------------------------------

    Component/s:     (was: wagon-http-lightweight)
                 wagon-http

> Proxy authentication not authenticating with settings
> -----------------------------------------------------
>
>                 Key: WAGON-116
>                 URL: http://jira.codehaus.org/browse/WAGON-116
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>         Environment: Linux with BlueCoat firewall/proxy
>            Reporter: Mykel Alvis
>             Fix For: 1.x
>
>         Attachments: myfile.txt
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (WAGON-116) Proxy authentication not authenticating with settings

Posted by "Tim Scott (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/WAGON-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135059#action_135059 ] 

Tim Scott commented on WAGON-116:
---------------------------------

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


> Proxy authentication not authenticating with settings
> -----------------------------------------------------
>
>                 Key: WAGON-116
>                 URL: http://jira.codehaus.org/browse/WAGON-116
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>         Environment: Linux with BlueCoat firewall/proxy
>            Reporter: Mykel Alvis
>             Fix For: 1.x
>
>         Attachments: myfile.txt
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Moved: (WAGON-116) Proxy authentication not authenticating with settings

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/WAGON-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved WAGONHTTP-14 to WAGON-116:
---------------------------------------------

    Affects Version/s:     (was: 1.0-beta-1)
                           (was: 1.0-alpha-6)
        Fix Version/s:     (was: 1.x)
                       1.x
                  Key: WAGON-116  (was: WAGONHTTP-14)
              Project: Maven Wagon  (was: wagon-http)

> Proxy authentication not authenticating with settings
> -----------------------------------------------------
>
>                 Key: WAGON-116
>                 URL: http://jira.codehaus.org/browse/WAGON-116
>             Project: Maven Wagon
>          Issue Type: Bug
>         Environment: Linux with BlueCoat firewall/proxy
>            Reporter: Mykel Alvis
>             Fix For: 1.x
>
>         Attachments: myfile.txt
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (WAGON-116) Proxy authentication not authenticating with settings

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/WAGON-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated WAGON-116:
-------------------------------

    Component/s: wagon-http-lightweight

> Proxy authentication not authenticating with settings
> -----------------------------------------------------
>
>                 Key: WAGON-116
>                 URL: http://jira.codehaus.org/browse/WAGON-116
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http-lightweight
>         Environment: Linux with BlueCoat firewall/proxy
>            Reporter: Mykel Alvis
>             Fix For: 1.x
>
>         Attachments: myfile.txt
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (WAGONHTTP-14) Proxy authentication not authenticating with settings

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/WAGONHTTP-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated WAGONHTTP-14:
----------------------------------

    Fix Version/s: 1.x

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

> Proxy authentication not authenticating with settings
> -----------------------------------------------------
>
>                 Key: WAGONHTTP-14
>                 URL: http://jira.codehaus.org/browse/WAGONHTTP-14
>             Project: wagon-http
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-6, 1.0-beta-1
>         Environment: Linux with BlueCoat firewall/proxy
>            Reporter: Mykel Alvis
>             Fix For: 1.x
>
>         Attachments: myfile.txt
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (WAGON-116) Proxy authentication not authenticating with settings

Posted by "Mykel Alvis (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/WAGON-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135122#action_135122 ] 

Mykel Alvis commented on WAGON-116:
-----------------------------------

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.


> Proxy authentication not authenticating with settings
> -----------------------------------------------------
>
>                 Key: WAGON-116
>                 URL: http://jira.codehaus.org/browse/WAGON-116
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>         Environment: Linux with BlueCoat firewall/proxy
>            Reporter: Mykel Alvis
>             Fix For: 1.x
>
>         Attachments: myfile.txt
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira