Add interface to handle authentication requests

[GoogleCodeExporter]

When authorization is required by a site or a proxy server, CEF cancels the 
request.  This patch adds an interface to CefHandler that allows the client to 
supply a username and password

Original issue reported on code.google.com by mikeyk...@gmail.com on 4 Dec 2010 at 1:03

Attachments:

• 149_auth.txt

[GoogleCodeExporter]

Looks good to me.

Original comment by magreenb...@gmail.com on 3 Jan 2011 at 5:20

• Changed state: Accepted

[GoogleCodeExporter]

mikeyk730, thanks for this patch; I'm trying to use CEF to connect to an 
authenticating proxy server, so this will really help.  I have one question 
about this patch.  When I use CEF to connect to an authenticating proxy server 
on Windows, a dialog pops up asking for my credential information 
(username/password).  As mentioned by you, without this patch, CEF cancels the 
request.  What I'm failing to understand is how I would access the 
username/password entered by the user in that dialog, so that I could then set 
it in HandleAuthenticationRequest.  Apolgies if I'm just misunderstanding.

Original comment by emerick on 5 Jan 2011 at 9:07

[GoogleCodeExporter]

Could you post a screenshot of the dialog that you are seeing?  There's nothing 
in the CEF and Chromium layers that I've seen that would trigger any sort of UI 
related to credentials (both before and after my patch)

My patch overrides OnAuthRequired which is called when the underlying network 
stack doesn't have credentials to provide to the server.  There is no UI 
associated with this, unless you (as a consumer of HandleAuthenticationRequest) 
choose to add one.  I should point out that the OnAuthRequired is the same 
method that Chrome overrides in order to show its custom credentials dialog.

Do you have any other information that may help determine what is going on.  Do 
you know the type of authentication the proxy uses, e.g NTLM vs. something else?

Original comment by mikeyk...@gmail.com on 7 Jan 2011 at 12:53

[GoogleCodeExporter]

It turns out that another component that I'm calling was posting an auth 
dialog.  I didn't realize I was calling into that, so I assumed that Chromium 
was posting the dialog (via calls to WinHttp in its proxy resolver).  Sorry for 
the confusion!

Original comment by emerick on 7 Jan 2011 at 12:58

[GoogleCodeExporter]

Thanks Mikey, committed as revision 158 with some minor style changes 
(indentation and line wrapping).

Original comment by magreenb...@gmail.com on 7 Jan 2011 at 1:25

• Changed state: Fixed

[GoogleCodeExporter]

is this still fixed because im not getting the chance to authenticate

Original comment by elimda...@gmail.com on 13 Feb 2015 at 3:30