Return-Path: X-Original-To: apmail-manifoldcf-user-archive@www.apache.org Delivered-To: apmail-manifoldcf-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8ED1D17BB4 for ; Mon, 23 Mar 2015 08:04:43 +0000 (UTC) Received: (qmail 60065 invoked by uid 500); 23 Mar 2015 08:04:37 -0000 Delivered-To: apmail-manifoldcf-user-archive@manifoldcf.apache.org Received: (qmail 60015 invoked by uid 500); 23 Mar 2015 08:04:37 -0000 Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@manifoldcf.apache.org Delivered-To: mailing list user@manifoldcf.apache.org Received: (qmail 60005 invoked by uid 99); 23 Mar 2015 08:04:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2015 08:04:37 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of daddywri@gmail.com designates 209.85.213.43 as permitted sender) Received: from [209.85.213.43] (HELO mail-yh0-f43.google.com) (209.85.213.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2015 08:04:12 +0000 Received: by yhch68 with SMTP id h68so64745292yhc.1 for ; Mon, 23 Mar 2015 01:01:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HtEa5wZBV/q1hHqzgRrsfA28MbqXIbEN52xSTQNrbFE=; b=Z+u32ZvZneK4Tkiiz6VCwPmQDZrd1OWiXwFFtM9fJ9+KmLiRTTqciRtKT0sRkfMnl3 WgAxq4ly/HbFU3miBKS1yNyggOwrna4rxh5NOAr8KxhqJ4TG+qyylSnwqk2VNomlwizE eavPjNx9OZwth4HR0T6X0o/3wFXsRbp8p14URaot2kJg50uxWXS/uOPVejjTa+kcIWfa vreIKBQm2t1tS8RywZZQ7lgv9AdgzDyx1LWbQU3/NvXkJipmDFTLMz4T8AfgQ958E9KF mp8VXVNHQlbOz2xQxbUMAH3MeUUexAraoImR9oqPyp0jBuKadx48oscwGymCTHRR4+Hx nOZw== MIME-Version: 1.0 X-Received: by 10.236.1.200 with SMTP id 48mr8457735yhd.64.1427097715278; Mon, 23 Mar 2015 01:01:55 -0700 (PDT) Received: by 10.170.107.130 with HTTP; Mon, 23 Mar 2015 01:01:55 -0700 (PDT) In-Reply-To: <5C27231EDA52F04091CE76701D50A76345BF983F@chnshlmbx11> References: <5C27231EDA52F04091CE76701D50A76345BF983F@chnshlmbx11> Date: Mon, 23 Mar 2015 04:01:55 -0400 Message-ID: Subject: Re: ManifoldCF Authentication From: Karl Wright To: "user@manifoldcf.apache.org" Content-Type: multipart/alternative; boundary=089e0112ca4a6107020511f014d6 X-Virus-Checked: Checked by ClamAV on apache.org --089e0112ca4a6107020511f014d6 Content-Type: text/plain; charset=UTF-8 Hi Smitha, As long as you provide some means of authentication in your web application, other than Active Directory, ManifoldCF can certainly do the authorization part. Karl On Mon, Mar 23, 2015 at 1:57 AM, Smitha S wrote: > Hi Karl, > > > > I have a requirement to crawl documents shared using window share and > index them to solr. The sharing permissions of window share decides which > user can access documents. The window share is under Active Directory. > > > > I have an web application where the search results are displayed. > Currently we are handling authentication and authorization with a DB > approach. > > > > Now we are planning to use the Authentication module of ManifoldCF to > decide the access rights of documents. Because of some client side > restrictions, I cannot use Active Directory for login into the web > application. In that case, do u see any challenges in using ManifoldCF for > providing access rights for documents? > > > > Thanks & Regards, > > Smitha S > > > > > > **************** CAUTION - Disclaimer ***************** > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely > for the use of the addressee(s). If you are not the intended recipient, please > notify the sender by e-mail and delete the original message. Further, you are not > to copy, disclose, or distribute this e-mail or its contents to any other person and > any such actions are unlawful. This e-mail may contain viruses. Infosys has taken > every reasonable precaution to minimize this risk, but is not liable for any damage > you may sustain as a result of any virus in this e-mail. You should carry out your > own virus checks before opening the e-mail or attachment. Infosys reserves the > right to monitor and review the content of all messages sent to or from this e-mail > address. Messages sent to or from this e-mail address may be stored on the > Infosys e-mail system. > ***INFOSYS******** End of Disclaimer ********INFOSYS*** > > --089e0112ca4a6107020511f014d6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Smitha,

As long as you provide some = means of authentication in your web application, other than Active Director= y, ManifoldCF can certainly do the authorization part.

=
Karl


On Mon, Mar 23, 2015 at 1:57 AM, Smitha S <Smitha_= S09@infosys.com> wrote:

Hi Karl,

=C2=A0

I have a requirement to crawl documents shared using= window share and index them to solr. The sharing permissions of window sha= re decides which user can access documents. The window share is under Activ= e Directory.

=C2=A0

I =C2=A0have an web application where the search res= ults are displayed. Currently we are handling authentication and authorizat= ion with a DB approach.

=C2=A0

Now we are planning to use the Authentication module= of ManifoldCF to decide the access rights of documents. Because of some cl= ient side restrictions, I cannot use Active Directory for login into the we= b application. In that case, do u see any challenges in using ManifoldCF for providing access rights for doc= uments?

=C2=A0

Thanks & Regards,

Smitha S

=C2=A0

=C2=A0

****=
************ CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solel=
y=20
for the use of the addressee(s). If you are not the intended recipient, ple=
ase=20
notify the sender by e-mail and delete the original message. Further, you a=
re not=20
to copy, disclose, or distribute this e-mail or its contents to any other p=
erson and=20
any such actions are unlawful. This e-mail may contain viruses. Infosys has=
 taken=20
every reasonable precaution to minimize this risk, but is not liable for an=
y damage=20
you may sustain as a result of any virus in this e-mail. You should carry o=
ut your=20
own virus checks before opening the e-mail or attachment. Infosys reserves =
the=20
right to monitor and review the content of all messages sent to or from thi=
s e-mail=20
address. Messages sent to or from this e-mail address may be stored on the=
=20
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

--089e0112ca4a6107020511f014d6--