Cannot authenticate user using SeaMonkey browser

[Ronald Dai]

The CAS server works with Firefox.

I think I have found the cause. There is a supportedBrowser list in the spnego code. It supports MSIE, Firefox, AppleWebKit, and SeaMonkey is not in this list. So I think this issue can be resolved by adding the SeaMonkey into this list. Could anyone confirm it? Thanks!



----- Original Message ----
From: Michael Ströder <michael at stroeder.com>
To: dai.ronald at yahoo.com; Yale CAS mailing list <cas at tp.its.yale.edu>
Sent: Friday, July 25, 2008 5:05:02 PM
Subject: Re: Cannot authenticate user using SeaMonkey browser

Ronald Dai wrote:
> 
> I have set up a CAS server, which authenticates the user with NTLM protocol.

Die you follow http://www.ja-sig.org/wiki/display/CASUM/SPNEGO for 
setting this up? Especially the property NTLMallowed and section "Set up 
Browser / Firefox"?

Does it work with Firefox? I'm asking because SPNEGO/Kerberos does not 
work anymore for me with Seamonkey. It used to work and it works with 
Firefox. Not sure which update caused this. :-/

See also:
http://groups.google.com/group/mozilla.dev.apps.seamonkey/browse_thread/thread/4a63c4086937e981/cb17405dede9f4ed?lnk=st&q=seamonkey+spnego#cb17405dede9f4ed

> when accessed the CAS login url using SeaMonkey, the CAS server returned 
> a HTTP 200 packet.

You can easily observe this also with http://livehttpheaders.mozdev.org 
which is also helpful when using SSL (which is a MUST with CAS).

> But using IE, the CAS server returned a HTTP 401
> packet.

Hmm, strange. Should be the same in both cases.

Ciao, Michael.



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20080725/d57e1ddf/attachment.html