Google SharePoint Connector full changelog

This patch contains fix for the following issues:
· Issue 5595594 Group resolution fails for special characters in group name
· Issue 5713953 SharePoint connector sets incorrect display URL for some of the object types
· Issue 5579962 Changes not detected when a SharePoint folder is moved within the same site
· Issue 5529449 SharePoint Connector does not exclude meta tag parentwebtitle
· Issue 5479101 SharePoint connector fails to add group member ship in the user datastore if groupname has more than 40 characters
· Issue 4672274 SharePoint connector should support all types of Site/list templates for sending ACLs to GSA
· Issue 4457286 SharePoint connector does not remove database tables when connector instance is deleted
· Issue 4081238 SharePoint connector not able to send correct MIME type for MS Outlook .msg files
· Issue 5408782 SharePoint connector fails to traverse a site, circular redirect exception is observed
· Issue 4903561 SharePoint connector has no validation for the LDA

· This patch contains fix for the following issues
· Issue 177/3290338: For ACL indexing, add ability to differentiate identical group names in SharePoint, Active Directory, and the local computer
· Description
· There is a discrepancy between the way GSA handles users and groups during ACL based authorization
· This discrepancy is mainly related to the format that GSA uses for usernames and group names while matching them with the entries in ACL
· For username, it uses just the username (without domain). But, for groups it uses domaingroupname. This, in turn, is because of the fact that
· while constructing the Primary Verified Identity, GSA strips off domain from username but it does not do the same with group names that are returned in response to a user group resolution query. The cookie cracker always returns the user or group name in the format domainusername or domaingroupname