Adding a connector may not force GSA to prompt for credentials

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Reset the index (that it, start with no content at all).
2. Add a connector and index content.
3. Delete the connector (but not the feed).
4. Open a browser and search for secure content.
5. GSA does not prompt for credentials and returns no search results.
6. Add the same connector back again.
7. Search for secure content again.

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

I expected the GSA to prompt for credentials after step 7, but it does not. It 
once again returns 
no results.

This is admittedly a strange sequence, but it's where I encountered the 
problem. There are two 
more natural variations that I have not tested. First, indexing connector 
content from scratch, 
that is, skip steps 2 and 3. Second, replace steps 1-3 with a step that indexes 
a different 
repository of secure content, through the connectors or otherwise.

What version of the product are you using? On what operating system?

GSA 5.0.0.G.14, Connector Manager 1.0.2.

Please provide any additional information below.

I don't know whether the same issue occurs if the GSA has prompted for 
credentials. Will it notice 
the new connector and validate the identity for that connector, or will it 
ignore newly indexed 
content for the duration of the browser session?

I may admittedly be unusual, but I typically leave my browser running for weeks 
at a time.

The GSA seems to be checking whether it needs to prompt for credentials, and 
then caching the 
results for the duration of the browser session. If you restart the browser 
between steps 5 and 7, 
the GSA correctly prompts for credentials after step 7.

P1, if you agree that search users should not have to restart their browsers to 
see new content, 
and if this same problem would occur in the two more natural scenarios. P3, if 
it really requires 
this specific scenario to trigger the bug, where the initial decision about 
prompting is made when 
there is secure content but no configured connector.

Original issue reported on code.google.com by jl1615@gmail.com on 20 Oct 2007 at 1:31

[GoogleCodeExporter]

Please research with 5.0.4

Original comment by donald.z...@gmail.com on 18 Apr 2008 at 10:27

• Changed state: Accepted

[GoogleCodeExporter]

John please verify, Marty probably fixed the issue where a first connector is 
added,
front end is not notified.

Original comment by jeffreyl...@gmail.com on 18 Apr 2008 at 10:29

[GoogleCodeExporter]

This is apparently still an issue using 5.0.4.G.22.
Clearing the access control cache has no effect

Original comment by Brett.Mi...@gmail.com on 11 Nov 2008 at 10:51

[GoogleCodeExporter]

Original comment by mar...@google.com on 4 Dec 2009 at 11:11

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by jla...@google.com on 25 Jun 2011 at 1:45

[GoogleCodeExporter]

This issue is filed as Google issue #6514018

Original comment by tdnguyen@google.com on 18 May 2012 at 9:47

• Changed state: Duplicate