search

googlegsa / sharepoint.v3

Google Search Appliance Connector for SharePoint
5 stars 10 forks source link

Google Searchbox - tested with Kerberos? #83

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Installed Google Search Box
2. Getting 200 response from GSA
3. Getting 401.2 Response from SharePoint.

What is the expected output? What do you see instead?
A search results page with the Google results.

What version of the product are you using? On what operating system?
Windows 2003, MOSS 2007, Windows Vista client and Windows Server 2003 
client.

Please provide any additional information below.

Haven't really seen a 401.2 before.  In debugging, the Google class 
returns the result.

Original issue reported on code.google.com by mbciz...@yahoo.com on 24 Jul 2009 at 4:39

GoogleCodeExporter commented 9 years ago 
Google Search Box does support Kerberos authN

2. Getting 200 response from GSA
Where did you find this? In the Windows Application event logs for Google 
Search Box?

3. Getting 401.2 Response from SharePoint.
This means that either IIS that hosts SharePoint is not correctly setup for 
Kerberos 
or there are problems with delegation and SPNs in your Active Directory 
configuration.

In order to get Search Box working with Kerberos, you need to enable Kerberos 
on both 
GSA and SharePoint.

Make sure you follow  all necessary steps to configure them correctly. Try 
searching 
from the GSA search console. You should get the search results without any 
prompt for 
user credentials. That being the case Search Box will work without any problems.

Share the logs from Application event log for more details and debugging.

Original comment by rakeshs101981@gmail.com on 24 Jul 2009 at 7:50

GoogleCodeExporter commented 9 years ago 
2. Saw that in the Windows Application Event

3. Thought that as well.  The GSA is triming the results, we are seeing the 
negotitate header come from IIS and seeing the kerberos login in the event 
viewer.

We did investigating.  It's working now...oddly.  I'd say close this issue and 
if I 
discover what was happening...I'll let you know.

Original comment by mbciz...@yahoo.com on 24 Jul 2009 at 9:11

GoogleCodeExporter commented 9 years ago 
Thanks.

Original comment by rakeshs101981@gmail.com on 24 Jul 2009 at 9:17

GoogleCodeExporter commented 9 years ago 
Actually, we did some more testing.  So if kerberos authentication fails, the 
user 
get's a 401 - remote server

We still have some users having the 401.2 error and other's getting search 
results.  
We'll continue to investigate.

Original comment by mbciz...@yahoo.com on 24 Jul 2009 at 9:33