My guess is that the account you are using is failing authentication (if you
are getting an invalid key) or authorization (the account you are using is
not allowed access), and Mozilla is not able to handle that failing over to
NTLM auth when Authorization fails with Negotiate.  Do you ever see a
password prompt?

-Christopher
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Friday, May 28, 2004 6:42 AM
To: [EMAIL PROTECTED]
Subject: Re: negotiateauth triggers endless loop asking KDC for ticket

Can anyone confirm that they are experiencing this as well?
I have reinstalled and reconfigured many times, with the same result.
Am I alone in this boat?

- Jim

Daniel Veditz <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> Probably better covered in the .netlib group
> 
> Jim Mulvey wrote:
> 
> > Hello,
> > 
> > I'm trying to get the negiotiateauth feature in the Mozilla 1.7 Beta
> > browser (on Red Hat 9) to authenticate to an IIS server. The Red Hat
> > server is using Kerberos-Workstation-1.3.3 (the latest) to
> > authenticate to the Windows domain.
> > 
> > However, when I try to access a secured page on the IIS server from
> > the Mozilla browser, the browser performs the following actions:
> > 
> > 1. Mozilla attempts a TGS-REQ to obtain a service ticket for the HTTP
> > service. According to Ethereal, the details of the request are as
> > follows:
> >       Server Name (Service and Host): HTTP server2003.jmulvey.local
> >           Name-type: Service and Host (3)
> >           Name: HTTP
> >           Name: server2003.jmulvey.local
> >       
> > 2. Mozilla attempts a TGS-REQ to obtain a service ticket for the
> > krbtgt service
> >       Server Name (Service and Host): HTTP server2003.jmulvey.local
> >           Name-type: Unknown (0)
> >           Name: krbtgt
> >           Name: JMULVEY.LOCAL
> > 
> > 3. Mozilla then makes a port 80 GET request to the webserver, with a
> > Negotiate string. The request is rebuffed by the IIS server as
> > Unauthorized.
> > 4. Mozilla repeats the process at step #2 above.
> > 
> > This yields an endless loop.
> > Any idea what is going on here?? Is this a bug? Any workarounds?
> > 
> > Thanks,
> > - Jim
_______________________________________________
Mozilla-security mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-security

_______________________________________________
Mozilla-security mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-security

Reply via email to