Authorization may fail against case-sensitive SQL Server

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a connector using Livelink backed by a SQL Server instance using a 
case-sensitive collation.
2. Perform a search with a valid user that should return results.

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

No results are returned. The logs contain the following error:

com.google.enterprise.connector.otex.client.lapi.LapiException: Error Listing 
requested Nodes (106601) Could not access specified items. (Error executing an 
Sql statement.)
        at com.google.enterprise.connector.otex.client.lapi.LapiClient.ListNodes(LapiClient.java:280)
        at com.google.enterprise.connector.otex.LivelinkAuthorizationManager.getNodeId(LivelinkAuthorizationManager.java:369)
        at com.google.enterprise.connector.otex.LivelinkAuthorizationManager.getExcludedVolumeId(LivelinkAuthorizationManager.java:350)
        at com.google.enterprise.connector.otex.LivelinkAuthorizationManager.<init>(LivelinkAuthorizationManager.java:86)

Please use labels and text to provide additional information.

The authorization fails due to case mismatch in a database column name. When 
SQL Server is using a case-sensitive collation, even table and column names are 
case-sensitive.

Original issue reported on code.google.com by jla...@google.com on 2 Mar 2011 at 6:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Fixed in revision 438.

Original comment by jla...@google.com on 3 Mar 2011 at 9:26

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****