Re: Authenticating Proxy Server

Emmanuel E <emmanuel.e@xxxxxxx> · Fri, 18 Apr 2008 09:45:36 +0530

No FF will not communicate to a proxy using SSL. It will communicate 

using SSL to any webserver via proxy or directly, but not to a proxy 

using SSL. Its not forbidden, but its not explicitly defined anywhere. 

Similar to bug http://issues.apache.org/bugzilla/show_bug.cgi?id=29744

Till Necko comes out I dont think it will be possible to tinker with the 

network code in mozilla.

So that leaves us with NTLM, Digest or Radius. Hope you are able to get 

something to work.

Neil A. Hillard wrote:

Hi,

Nick Kew wrote:

On Thu, 17 Apr 2008 15:28:19 +0100
Roy Pearce <R.A.Pearce@xxxxxxxxxx> wrote:

Sounds to me like a browser misconfiguration.

All I changed was the port number to point to a secure 

authenticating proxy server.

It appears that FF assumes the proxy server is talking HTTP when I
would like it to talk HTTPS.

Sorry, I'm no expert on firefox.  Did you try its "about:"?
I expect there's a plugin for it, it it really isn't builtin.

HTTP digest authentication.

We can't use Digest as the password file is not on the same machine.
We use mod_auth_radius to connect to a RADIUS server (on another
machine) to check credentials against the ADF database.

One of the changes in 2.2 over earlier versions is that the HTTP
authentication method (Basic/Digest/Homebrew) is decoupled from
the backend lookup (radius, in your case).  So that's no longer
an issue, assuming the radius authentication module has been
updated to use the new framework.

We (as Nick knows) had major problems with mod_auth_radius so we 

commissioned mod_auth_xradius

http://www.outoforder.cc/projects/apache/mod_auth_xradius/

which should be fully compatible with Apache 2.2.

HTH,

                Neil.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx