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 9077C995D for ; Mon, 15 Dec 2014 11:50:02 +0000 (UTC) Received: (qmail 55846 invoked by uid 500); 15 Dec 2014 11:50:02 -0000 Delivered-To: apmail-manifoldcf-user-archive@manifoldcf.apache.org Received: (qmail 55793 invoked by uid 500); 15 Dec 2014 11:50:02 -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 55772 invoked by uid 99); 15 Dec 2014 11:50:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 11:50:02 +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.50 as permitted sender) Received: from [209.85.213.50] (HELO mail-yh0-f50.google.com) (209.85.213.50) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 11:49:36 +0000 Received: by mail-yh0-f50.google.com with SMTP id 29so5379495yhl.37 for ; Mon, 15 Dec 2014 03:49:35 -0800 (PST) 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 :cc:content-type; bh=SUMomPfhe0gpn30te7ve3G0Bavu/bZUBl+jXb+j4Ukg=; b=MvzNPkKB9CiXbkpn0FLSghhRLrn2EkXgDpwv9U2F3b7ehDzCG3pgk5kB0EcQl1mHEb w/OfJ5vEY/7JaclF0c1q2hMx3uGkhwQCLMGv5CaEDiUAmqH8ixL3Aw5Q5j+uI40oE+2f j+8hq+eHVRPlojUurrsZmSMkD3xEDtx6slO3+YcvfhSSaSEJcVhdCSxYN21ixlUGcUKC YXGkLND5Jk9iLaJ8peaUVurNuJV7pyQeXUZ4uAIQ2OUcmdcuDvAfr7/8nUrVA7b/a0Dp 5RLA08qWrnf1gQflPdEHDiCmLQ20UuMbiLA9d2ovwqfs6L+BOEJCbXQjNPX0z77I/9A+ QYyw== MIME-Version: 1.0 X-Received: by 10.170.135.132 with SMTP id b126mr24430888ykc.6.1418644175803; Mon, 15 Dec 2014 03:49:35 -0800 (PST) Received: by 10.170.205.65 with HTTP; Mon, 15 Dec 2014 03:49:35 -0800 (PST) In-Reply-To: <5C27231EDA52F04091CE76701D50A76345B9EA40@chnshlmbx11> References: <5C27231EDA52F04091CE76701D50A76345B9EA40@chnshlmbx11> Date: Mon, 15 Dec 2014 06:49:35 -0500 Message-ID: Subject: Re: User permission for crawling windows share From: Karl Wright To: "user@manifoldcf.apache.org" Cc: "user-help@manifoldcf.apache.org" Content-Type: multipart/alternative; boundary=001a1139fd6c295a16050a3fd6e1 X-Virus-Checked: Checked by ClamAV on apache.org --001a1139fd6c295a16050a3fd6e1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Smitha, Can you tell me what version of MCF you are using? There was a fix for this very situation made a while ago, if I recall correctly. Karl On Mon, Dec 15, 2014 at 2:51 AM, Smitha S wrote: > > Hi, > > > > We are using ManifoldCF to crawl using window share repository connector. > In the fileserver a folder has been shared to a specific user (e.g say > mcfusr). We have configured the window share repository connector with th= e > server details, domain and the user credentials for =E2=80=98mcfusr=E2=80= =99. But when we > ran the mcf job, crawling failed with an exception =E2=80=9Cjcifs: possib= ly > trasient exce detected while getting share security=E2=80=9D. > > > > When I went through the mailing list, I found a related thread. > > > http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201409.mbox/%3C2= 77F6D86-4C79-4C61-8AEF-FD5CD3D72737@gmail.com%3E > > > > As per this, we have added the =E2=80=9Cmcfusr=E2=80=9D to the administra= tor group of the > fileserver. The crawling job worked successfully. But with this > configuration, we found another issue. > > > > In the fileserver, there is another shared folder which is shared with > only some other user (say restricted_folder). This folder is not shared > with =E2=80=9Cmcfuser=E2=80=9D explicitly. From outside the fileserver, w= e are not able to > access this restricted folder. But we are able to configure the crawling > job with this folder and mcfuser. The crawling is successful and document= s > are successfully indexed. > > > > Even though MCF reads the ACL of the folder and its contents, why is it > allowed for mcfusr to crawl the documents. We were expecting an exception > in this scenario. Because of this our client is a little reluctant to add > mcfusr to administrative group. > > > > Could you please provide us some light on this. > > > > Thanks & Regards, > > Smitha S > > > > **************** CAUTION - Disclaimer ***************** > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol= ely > for the use of the addressee(s). If you are not the intended recipient, p= lease > 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 h= as 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 reserve= s the > right to monitor and review the content of all messages sent to or from t= his e-mail > address. Messages sent to or from this e-mail address may be stored on th= e > Infosys e-mail system. > ***INFOSYS******** End of Disclaimer ********INFOSYS*** > > --001a1139fd6c295a16050a3fd6e1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Smitha,

Can you tell me what version of MCF you = are using?=C2=A0 There was a fix for this very situation made a while ago, = if I recall correctly.

Karl

=
On Mon, Dec 15, 2014 at 2:51 AM, Smitha S <Smitha_S09@infosys.com> wrote:

Hi,

=C2=A0

We are using ManifoldCF to crawl using window share = repository connector. In the fileserver a folder has been shared to a speci= fic user (e.g say mcfusr). We have configured the window share repository c= onnector with the server details, domain and the user credentials for =E2=80=98mcfusr=E2=80=99. But when we = ran the mcf job, crawling failed with an exception =E2=80=9Cjcifs: possibly trasient exce detected= while getting share security=E2=80=9D.

= =C2=A0

When I went through the mailing list, I found a rela= ted thread.

= http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201409.mbox/%3C2= 77F6D86-4C79-4C61-8AEF-FD5CD3D72737@gmail.com%3E

=C2=A0

As per this, we have added the =E2=80=9Cmcfusr=E2=80= =9D to the administrator group of the fileserver. The crawling job worked s= uccessfully. But with this configuration, we found another issue.=

=C2=A0

In=C2=A0 the fileserver, there is another shared fol= der which is shared with only some other user (say restricted_folder). This= folder is not shared with =E2=80=9Cmcfuser=E2=80=9D explicitly. From outsi= de the fileserver, we are not able to access this restricted folder. But we are able to configure the crawling job with this folder and= mcfuser. The crawling is successful and documents are successfully indexed= .

=C2=A0

Even though MCF reads the ACL of the folder and its = contents, why is it allowed for mcfusr to crawl the documents. We were expe= cting an exception in this scenario. Because of this our client is a little= reluctant to add mcfusr to administrative group.

=C2=A0

Could you please provide us some light on this.

=C2=A0

Thanks & Regards,

Smitha S

=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***
--001a1139fd6c295a16050a3fd6e1--