Connector accepts username in format user@domain for user when SharePoint site mentioned under crawl URL is a HTTP basic protected site

[GoogleCodeExporter]

What steps will reproduce the problem?
1. While configuring the connector, enter valid domain, username and 
password.
2. Click on "Save Configuration" to save the connector configuration.

Expected output: 
Connector configuration should get saved and connector should start 
crawling sharepoint documents.

What do you see instead?
The configuration is not saved and warning message "cannot connect to 
given sharepoint URL with supplied Domain/Username/Password. Please re-
enter" gets displayed.

Workaround:
Keep domain field blank. Enter the UserName as "user@domain" instead of 
just "user". 

Note: This issue gets reproduced ONLY for domain users. For local users 
(users on the same machine where the sharepoint server is installed), 
there is no deviation from the original behaviour.

Original issue reported on code.google.com by amit.per...@gmail.com on 12 Nov 2008 at 6:34

[GoogleCodeExporter]

See Connector Manager Issue 131:
http://code.google.com/p/google-enterprise-connector-manager/issues/detail?id=13
1

The Connector Manager now includes the domain in the AuthenticationIdentity. 
Unfortunately, older GSAs do not supply the domain.
The connectors should be enhanced to:
  1) Use the domain specified in the AuthenticationIdentity if present.
      (Older GSAs won't pass the domain.). 
  2) Use the domain specified in the connectorInstance.xml, if one
      was not received from the GSA.

Original comment by Brett.Mi...@gmail.com on 16 Mar 2009 at 9:31

[GoogleCodeExporter]

The reported issue was because of the Axis stub behavior as it accepts username 
in
different format depending on the authentication scheme applied on the web
application. As a fix, connector assumes NTLM as the default authentication 
scheme
being used. If the call fails with a HTTP response 404, then it tries with the 
format
appropriate for HTTP Basic. Proper optimizations has been done to reduce the
redundant calls as much as possible. Though, HTTP Basic users will surely 
suffer with
some extra remote calls by the connector.

For AuthN and AuthZ, appropriate changes has been done as suggested by
Brett.Michael.Johnson in reference to Connector Manager Issue 131 above.

Original comment by th.nitendra on 24 Jun 2009 at 11:40

• Changed state: Fixed

[GoogleCodeExporter]

Verified in 2.0.0 and works fine.

Original comment by shashank...@gmail.com on 25 Jun 2009 at 12:07

• Changed state: Verified