Item13382: Authentication data in {PROXY}{HOST}
Priority: Normal
Current State: Confirmed
Released In: n/a
Target Release: n/a
Applies To: Engine
Component: Configure
Branches: master
I installed 1.2.0 beta. My server is behind a proxy that requires authentication. Thus, I need to set {PROXY}{HOST} to be able to install extensions via configure. The help says "If your proxy requires authentication, simply put it in the URL,
as in:
http://username:password@proxy.your.company".
However, configure's AJAX checker tells me "Embedded authentication is not permitted in
http://domain\username:password@proxy.server". I originally thought the configure checker is incorrect.
... But maybe not. After checking that
LocalSite.cfg contains the correct username and password in {PROXY}{HOST}, I get this error when trying to search for an extension from within configure:
Error accessing Foswiki.org: Proxy Authentication Required
FWIW, configure does not complain in 1.1.9, but I get a similar error (Error accessing Foswiki.org: Proxy Authentication Required) when I try to "find more extensions" within 1.1.9's configure. I checked: LWP is being used (i.e. _GETUsingLWP is being called).
It would appear that the proxy uses NTLM authentication. If so, can this work?
Two issues, then:
- The {PROXY}{HOST} help says to put the proxy username and password in the proxy URL, and the configure checker says that is not permitted.
- I didn't see any mention of support (or otherwise) for NTLM proxies.
I've checked in a fix for the checker. The syntax wasn't quite implemented correctly.
The NTLM auth, LWP appears to support NTLM auth, but Foswiki doesn't enable that option. It appears it would need some surgery on
Foswiki::Net
. It would also pull in some additional dependencies for the Authen::NTLM module.
--
GeorgeClark - 25 Apr 2015
The warning wasn't very nice, actually it was plain wrong, because it works anyway, even with url-encoded special characters in the password.
--
FranzJosefGigler - 25 Apr 2015