[jetty-dev] Jetty Spnego instruction ktpass - why only crypto RC4-HMAC-N

["Houtman, Roland" <Roland.Houtman@xxxxxxxxxxxxxxx>]

Dear Devs,

 

At a customer site, the client browser sends a negotiate header, but the server side fails with a checksum failed error. It seems to be related to the used cipher suite.

 

The online jetty documentation tells to use ‘ktpass’ with specifically RC4-HMAC-NT

http://www.eclipse.org/jetty/documentation/current/spnego-support.html

 

Does Jetty only support RC4-HMAC-NT?

 

Is there anything on the browser/client side which can be done to enforce the particular RC4 cipher?
(I would expect spnego/kerberos does auto-selection)

 

 

Looking at http://www.eclipse.org/jetty/mailinglists.php

this mailing-list seemed most suited for the question. If not, please advise.

 

Kind regards,

Roland