[THIN] Re: Web Interface Single Sign On
- From: "Malcolm Bruton" <malcolm.bruton@xxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Mon, 2 Apr 2007 11:22:02 -0400
I found the resolution to this today.
Basically when we turned on the SSO option in WI some users would get an HTTP
400 Bad request page. If you clicked refresh it would work. Also if you used
the IP address it would work for the same user. Other users could use the WI
page without issue
If you have a large AD infrastructure it is possible to have a large Kerberos
ticket. IIS can't handle this without a few tweaks.
for IIS 5.0 for increase HKLM\System\CCC\Services\W3SVC\MaxClientRequestBuffer
for IIS 6 increase HKLM\System\CCC\Services\HTTP\MaxFieldLength and
MaxRequestBytes
We used 32768.
Hope this helps somebody else.
Malcolm
________________________________
From: thin-bounce@xxxxxxxxxxxxx on behalf of Malcolm Bruton
Sent: Mon 26/03/2007 14:18
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Web Interface Single Sign On
Built a new WI 3.0 box today to play with and it worked without issue. Might
be time to either bounce my WI boxes which have been up the last 6 months or
blat the config and put it back.
Malcolm
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of
christopher.walter@xxxxxxx
Sent: 23 March 2007 13:43
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Web Interface Single Sign On
I've had this before and it was one of two things:
1. Try put the following in the registry on the any servers you have in
your serverlist within the web interface.
2. Try changing the servers in your serverlist. If this works then
chances are one of the servers in your server list is having performance
problems.
I had this same problem back about 6 months ago and can't remember which one I
did to fix it.
Thanks,
Chris
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Malcolm Bruton
Sent: Friday, March 23, 2007 6:49 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Web Interface Single Sign On
Have been running Web Interface 3 for some time.
If I check the Single sign-on check box.
Any users that now go to WI get a page not found error. However if I try the
same directly on the WI server it works fine.
Ideas? Client setting?
Malcolm
Other related posts:
