Thanks Karl.

We are using ManifoldCF 1.6. But the CONNECTORS-886 is added to MCF 1.6.1.

We will try to upgrade the version and test the scenario.

Thanks & Regards,
Smitha S

From: Karl Wright [mailto:[email protected]]
Sent: Monday, December 15, 2014 6:40 PM
To: [email protected]
Subject: Re: User permission for crawling windows share

Hi Smitha,
The support for folder security was added in MCF 1.6.  See CONNECTORS-886.

Karl

On Mon, Dec 15, 2014 at 6:49 AM, Karl Wright 
<[email protected]<mailto:[email protected]>> wrote:
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 
<[email protected]<mailto:[email protected]>> 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 the server details, 
domain and the user credentials for ‘mcfusr’. But when we ran the mcf job, 
crawling failed with an exception “jcifs: possibly trasient exce detected while 
getting share security”.

When I went through the mailing list, I found a related thread.
http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201409.mbox/%[email protected]%3E

As per this, we have added the “mcfusr” to the administrator 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 
“mcfuser” explicitly. From outside 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.

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 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***


Reply via email to