Cannot authenticate user using SeaMonkey browser

[Michael Ströder]

Michael Ströder wrote:
> Scott Battaglia wrote:
>> On Fri, Jul 25, 2008 at 12:32 PM, Michael Ströder <michael at stroeder.com 
>> <mailto:michael at stroeder.com>> wrote:
>>
>>     I'd prefer to maintain a black-list (unSupportedBrowser list) of
>>     misbehaving browsers not correctly ignoring unknown HTTP headers instead
>>     of having to maintain a white-list of well-behaving browsers
>>     (supportedBrowser list).
>>
>> Haha I just suggested the same thing!  I'm waiting for our SPNEGO 
>> developer to reply back to this list.
> 
> Then chances are not so bad that this get changed? ;-)
> 
> Ok, let's wait what Arnaud says.

Well, it's been a while since this conversation. Any chance to get this 
fixed?

In the mean-time I tried to extend the supportedBrowser property in 
cas-servlet.xml like this:

------------------------------- snip -------------------------------
	<bean id="negociateSpnego" 
class="org.jasig.cas.support.spnego.web.flow.SpnegoNegociateCredentialsAction">
		<property name="supportedBrowser">
			<list>
				<value>Seamonkey</value>
				<value>MSIE</value>
				<value>Firefox</value>
				<value>AppleWebKit</value>
			</list>
		</property>
	</bean>
------------------------------- snip -------------------------------

But it does not work (header WWW-Authenticate: Negotiate  not sent). How 
to find out which value I have to put there for Seamonkey 1.1.x?

Ciao, Michael.