-
15. Re: Basic Negotiation (in toolkit) not using SPNEGO
That sounds like a fun and exciting problem!
The only thing I can think of is to ensure that BOTH accounts have correctly configured their browsers to trust the web server you're testing.
If everything is good there, I would reset the password on the account that is not working and see if that changes anything. Sometimes, there are strange issues with the KDC when using an account that's never changed its password. It has not happened to me, but I've read about others fixing their issues by doing it.
If you still don't have any luck, I would suggest that you get your hands dirty with wireshark and see what's going on between your client, server, and the KDC.
Good Luck!
-
16. Re: Basic Negotiation (in toolkit) not using SPNEGO
Thx for answering, John! I have tried with Firefox Portable now. You only have to add your server URL to trusted URIs to get it working. ..which I did for both accounts. And I obtained the same result as with IE: It is doing its job on one, but not the other account. Looks like it's not about browser settings.
Robert
-
17. Re: Basic Negotiation (in toolkit) not using SPNEGO
I have solved it. This had nothing to do with SPNEGO. The authorization header of my request was too long, which results in a BadRequest (HTTP 400). You can adapt the header size in JBOSS_HOME/server/cce/deploy/jbossweb.sar/server.xml. You have to set "maxHttpHeaderSize" within the HTTP connector:
<Connector protocol="HTTP/1.1" port="8080" address="${jboss.bind.address}"
connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="32768" />Robert