manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1511) ManifoldCF 2.10 & Sharepoint 2013
Date Tue, 26 Jun 2018 15:46:00 GMT

    [ https://issues.apache.org/jira/browse/CONNECTORS-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523882#comment-16523882
] 

Karl Wright commented on CONNECTORS-1511:
-----------------------------------------

This is not the right way to get help for Sharepoint connector configuration.  Please post
to user@manifoldcf.apache.org.  I'll be happy to respond there.


> ManifoldCF 2.10 & Sharepoint 2013
> ---------------------------------
>
>                 Key: CONNECTORS-1511
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1511
>             Project: ManifoldCF
>          Issue Type: Bug
>    Affects Versions: ManifoldCF 2.10
>            Reporter: ArjanL
>            Priority: Major
>             Fix For: ManifoldCF 2.11
>
>         Attachments: IMG_20180626_161621.jpg
>
>
> We want to crawl the contents of a SharePoint 2013 installation from ManifoldCF.
> From a browser everything seems to works correctly. I can log in into Windows with the
crawler user credentials and then access SharePoint through the browser. From there I can
reach the site collection for which this user has authorization.
> Steps I have taken:
> - I already installed the plugin on the SharePoint 2013 server (MCPermissions). This
seems to be working.
> - Configured the repository in Manifold.  See attachment. We used Active Directory (not
SharePoint authorization)
> - Active Directory Authority works correct ManifoldCF says (using same crawler user credentials).
> My Manifold settings:
> !IMG_20180626_161621.jpg!
> If I inspect the Manifold logfile, is see that it is trying to access the SharePoint
root (for which we do not have authorization) instead of the mentioned site collection from
the configuration. *Actually, it looks like it is not using the configuration that I provided
in the web interface.* 
> Upgrading Manifold from 2.8.1 to 2.10 did not help....  (well... we did not expect that,
but wanted to everything possible)
>  Can someone help us where to look next?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message