Updates:
Labels: mstone5 Internals-Network
Comment #11 on issue 29862 by da...@chromium.org: Use SSPI on Windows
clients for automatic login to generate tokens for NTLM and Negotiate
http://code.google.com/p/chromium/issues/detail?id=29862
(No comment was entered for this change.)
--
Comment #9 on issue 29862 by w...@chromium.org: Use SSPI on Windows clients
for automatic login to generate tokens for NTLM and Negotiate
http://code.google.com/p/chromium/issues/detail?id=29862
I see -- that makes sense. If Negotiate chooses Kerberos, we
need to log in to Kerberos first, an
Comment #8 on issue 29862 by cbent...@chromium.org: Use SSPI on Windows
clients for automatic login to generate tokens for NTLM and Negotiate
http://code.google.com/p/chromium/issues/detail?id=29862
With Negotiate, AcquireCredentialsHandle was clearly failing when I entered
an invalid
User
Comment #5 on issue 29862 by cbent...@chromium.org: Use SSPI on Windows
clients for automatic login to generate tokens for NTLM and Negotiate
http://code.google.com/p/chromium/issues/detail?id=29862
Once I started implementing this I noticed that if I entered an invalid
username/password combin
Comment #2 on issue 29862 by cbent...@google.com: Use SSPI on Windows
clients for automatic login to generate tokens for NTLM and Negotiate
http://code.google.com/p/chromium/issues/detail?id=29862
Also - NTLM is currently supported but Negotiate is not.
--
You received this message because you
Comment #1 on issue 29862 by cbent...@google.com: Use SSPI on Windows
clients for automatic login to generate tokens for NTLM and Negotiate
http://code.google.com/p/chromium/issues/detail?id=29862
Issue 29596 is related and covers how to determine whether the server is
within the
intranet.
-
