Closed GoogleCodeExporter closed 9 years ago
Original comment by rakeshs101981@gmail.com
on 7 Aug 2009 at 2:17
Original comment by rakeshs101981@gmail.com
on 19 Aug 2009 at 4:30
Provided support for Kerberos Authentication at crawl time.
A new field KDC host name is added to the connector configuration page. This
field is
non-mandatory field. If user provides value for this field then Kerberos scheme
will
get selected for AuthN. If this field is left balnk then NTLM or Basic scheme
will be
chosen by connector to crawl the data.
Following are the major use cases which are handled while implementing Kerberos
support:
1. KDC server field left blank: In this case ntlm or basic authentication
should be
automatically selected by conenctor while crawling.
2. KDC server field is non-blank:
a. Valid IP Address: Configuration will get saved successfully
i. Site supports Kerberos: Then Negotiate Authentication scheme selected.
ii. Site does not supports Kerberos: NTLM or Basic scheme will get selected.
b. Invalid IP Address: "Please specify a fully qualified hostname for the
Kerberos Key Distribution Center (KDC)" error message will be displayed on the
screen
and configuration will not save.
c.FQDN KDC server name: Configuration will get saved successfully
i. Site supports Kerberos: Then Negotiate Authentication scheme selected.
ii. Site does not supports Kerberos: NTLM or Basic scheme will get selected.
d. Non-FQDN KDC Server Name: "Please specify a fully qualified hostname for the
Kerberos Key Distribution Center (KDC)" error message will be displayed on the
screen
and configuration will not save.
Original comment by pankajch...@gmail.com
on 6 Nov 2009 at 12:33
Fixed Revision:
http://code.google.com/p/google-enterprise-connector-sharepoint/source/detail?r=
382
http://code.google.com/p/google-enterprise-connector-sharepoint/source/detail?r=
381
http://code.google.com/p/google-enterprise-connector-sharepoint/source/detail?r=
380
Original comment by pankajch...@gmail.com
on 6 Nov 2009 at 12:34
Verified in 2.4 Release
Original comment by ashwinip...@gmail.com
on 14 Dec 2009 at 6:21
Original issue reported on code.google.com by
jeffreyl...@gmail.com
on 22 May 2009 at 3:12