Hi Yuvaraj, For any of the Active Directory authorities, you do the same thing. You supply the DNS name or IP address of your Active Directory domain controller. I thought you had gotten this working for an non-Claims-based system already? The values you supply for the SharePoint/ActiveDirectory authority are the same as those you would provide for the standard ActiveDirectory authority.
If you've never done this before, I suggest you read the manual: http://manifoldcf.apache.org/release/trunk/en_US/end-user-documentation.html#sharepointadauthority Karl On Thu, Mar 6, 2014 at 7:03 AM, yuvaraj ponnuswamy <[email protected]>wrote: > HI Karl, > > I am using the claim based authentication for the share point and as per > the End-User document should configure the SharePoint/ActiveDirectory > authority connection. > > 1) For the Authority groups , I have specified the AD Group name for my > user id.Is that correct.I have more than one group for my user id. > > 2) For the Auhtority Connections, I need to specify the following fields. > > Domain controller name : > Domain suffix : > Administrative user name -a4nm2 > Administrative password - somepassword > Authentication - DIGEST-MD5 GSSAPI > Login name AD attribute - sAMAccountName > > Can you please let me know what is that we need to give for Domain > controller name.Is it the active directory domain name? > > Also, what is the value we should give for the other fields. > > Can you please little eloborate on that. > > Thanks > P.Yuvaraj Kumar > > > > > *From:* Karl Wright <[email protected]> > *To:* "[email protected]" <[email protected]>; yuvaraj > ponnuswamy <[email protected]> > *Sent:* Monday, 3 March 2014, 21:52 > *Subject:* Re: when connecting MCF to Share Point with Claim Space > authentication > > Hi Yavaraj, > > HttpClient will support Kerberos-only authentication ONLY if you point the > JVM at the place where Kerberos tickets reside using a -D switch, and you > have some other process which keeps the tickets fresh. We therefore do not > recommend this configuration. Most SharePoint IIS setups we see have > either NTLM or SPNEGO with Kerberos as a primary authentication mechanism, > and NTLM as a secondary. > > Karl > > > > On Mon, Mar 3, 2014 at 11:18 AM, yuvaraj ponnuswamy < > [email protected]> wrote: > > Hi Karl, > > So, Claim based authentication will work on MCF 1.5.1 (latest release). > Can i know will it work for both Claims with NTLM and Claims with kerberos. > > Thanks for the information. > > > Regards > P.Yuvaraj Kumar > *From:* Karl Wright <[email protected]> > *To:* "[email protected]" <[email protected]>; yuvaraj > ponnuswamy <[email protected]> > *Sent:* Monday, 3 March 2014, 21:39 > *Subject:* Re: when connecting MCF to Share Point with Claim Space > authentication > > Hi Yuvaraj, > > Claims Based authentication is not supported until MCF 1.5.1. > > Karl > > > > On Mon, Mar 3, 2014 at 10:57 AM, yuvaraj ponnuswamy < > [email protected]> wrote: > > > Hi Karl, > > Currently we are using the ManifoldCF version 1.2 to connect to the Share > point url in our dev environment, > When we tried to connect ManifoldCF to SharePoint without claim space > authentication it is working fine. > But when we tried to connect MCF to SharePoint with Claim Space > authentication it is giving some error message and not working. > We need the MCF to be connected with share point with Claims with NTLM and > Claims with Kerberos > Can you please let me know your suggestions. > > > Error: > Unknown SharePoint server error accessing site - axis fault = Server, > detail = Server was unable to process request > ---> The source was not found, but some or all event logs could not be > searched. Inaccessible logs: Security. > > Thanks > P.Yuvaraj Kumar > > > > > > > >
