search

superdevo / google-enterprise-connector-sharepoint

Automatically exported from code.google.com/p/google-enterprise-connector-sharepoint
0 stars 0 forks source link

Search Box does not work when Security Manager is enabled on GSA. #127

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Test environment:
Windows 2003 SP2, MOSS 2007, HTTP Basic site

What steps will reproduce the problem?
1. Install GSBS using GRK.
2. Configure the search box for HTTP Basic site on SharePoint.
3. Configure Security Manager on GSA (see attached GSA_Sec_mgr_settings)
4. Perform search from the Search box.
5. Universal login Form appears. Enter valid credentials in the ULF.

What is the expected output? What do you see instead?

Expected result:
Search results should be shown to the user when valid credentials are 
entered in the ULF.

Actual result:
Search box shows the ULF again and again. No search results are shown.

Please use labels and text to provide additional information.
Version:GSBS 1.1.1
Attachments:
1. GSBS logs when search is performed
2. HTTP Headers for GSA search search with Security Manager enabled
3. ULF shown when search is performed on GSBS
4,5. GSA Security Manager settings

Original issue reported on code.google.com by shashank...@gmail.com on 4 Dec 2009 at 1:04

Attachments:

GoogleCodeExporter commented 9 years ago 
Since Security Manager is required in 6.4, this means that GSBSP is not 
compatible with 6.4.  I have verified that this is a problem with 6.4.0.G.6.

Original comment by bfowler%...@gtempaccount.com on 20 Aug 2010 at 9:46

GoogleCodeExporter commented 9 years ago 
These are the last few lines from SecMgr log:

[.security.authncontroller.AuthnSession.updateOutgoingCookies] sid 
a905d681c0cae53010f3e4e693391084: Outgoing cookies to user agent: (none)
100903 13:03:14.423:I 14 [.security.authncontroller.BackEndImpl.authenticate] 
sid a905d681c0cae53010f3e4e693391084: Leaving authentication controller in 
state AUTHENTICATING with result SUCCESSFUL
100903 13:03:14.432:X 14 
[org.opensaml.saml2.binding.encoding.BaseSAML2MessageEncoder.checkRelayState] 
Relay state exceeds 80 bytes, some application may not support this.
100903 13:03:14.433:I 14 
[.security.authncontroller.AuthnSession.setStateInternal] sid 
a905d681c0cae53010f3e4e693391084: State transition from AUTHENTICATING to IDLE
100903 13:03:41.183:I 11

Original comment by jeffl...@google.com on 3 Sep 2010 at 10:53

GoogleCodeExporter commented 9 years ago 
Since SecMgr support various authentication mechanisms, but for search box, 
Kerberos and SAML are much more important.

Original comment by jeffl...@google.com on 5 Sep 2010 at 7:46

GoogleCodeExporter commented 9 years ago

Original comment by shashank...@gmail.com on 18 Mar 2011 at 12:06

GoogleCodeExporter commented 9 years ago 
This issue is filed as Google issue #6513913

Original comment by tdnguyen@google.com on 17 May 2012 at 11:57