Hi Karl, hi Paul,
thank you very much for your serious answers and picking up this issue
immediately ... Maybe it will make sense to link CONNECTORS-1247 with
CONNECTORS-1133 (Connector for Sharepoint Office 365).
During our project we've done the following things:
1. grab all content (less content dependent configuration changes)
2. user authentication (multiple SP identities for one physical person)
3. added proxy support (authority- and repository-connector)
4. Improved mime type detection by using TIKA (for MS Visio files)
5. re-implementing PermissionsSoap interface (no plugin on the SP farm)
a) getPermissions
b) getListItems
The year now draws to a close and the capacities are becoming scarce.
Anyways if there is some point we can support the development of
CONNECTORS-1247, please let me know. We have a SharePoint 2013 farm as
well as a Office 365 installation available here (not for the public).
So at least I would be happy to be a tester for the REST API connector.
regards
-Rüdiger
-------------
to 1) In our approach we are trying to grab as much items/elements as
possible and than filter out the ones we are not interested in. Why? We
want to avoid Job configuration at runtime that depends on the SP
content. A new library for example should be indexed immediately without
adding it explicitly to the job's config.
to 2) We are using form based authentication for the repository
connection while we're using SAML 2.0 as SSO at search time. SP holds
multiple identities (one for each directory service, plus one local,
plus one for SAML) for the same physical person. This challenges us to
select the correct identity (at index- and at search-time). Finally we
introduced a claim configuration option to the authority- and the
repository-connector making the user selection unambiguous.
to 3) because we still on ManifoldCF version 1.7.1 we extended both the
authority- and repository-connector for proxy support. (I know that this
has also be done for the newer versions of ManifoldCF as well.
to 4) We improved the mime type detection by using TIKA in order to
support MS Visio files.
to 5a) because our application management is not willing to install
third-party plugins on the SP Fram, we implemented the
com.microsoft.sharepoint.webpartpages.PermissionsSoap interface against
the REST-Webservice. For keeping changes as small as possible, I
reconstruct a SOAP-Envelop based on the REST-Webservice response.
to 5b) because the SP SOAP service has problems with lists of more than
10.000 elements, we implemented the getListItems method as well against
the REST-Webservice. Unfortunately we ran into problems on our
production system with that code, what drove us to reject the
implementation against the REST-Webservice and return to the older one.
------------
Am 26.10.2015 um 18:43 schrieb Karl Wright:
Hi Paul,
That's great news!
I found previous discussion about SharePoint's REST API in an older
ticket, but we really need an explicit ticket for this work, so I
created one: CONNECTORS-1247.
The first issue to tackle is authenticating. It uses OAuth, as far as I
can tell, so we need to automate that in some way. I'll therefore start
by creating a runt connector instance that does only connection and
connection verification (which should be hard enough!) and see if we can
get that to work right.
I'm quite busy at work at the moment, so it will likely be this weekend
before I can put any time into getting started on this project. In the
meantime, if you want to do something (other than getting the instance
up and running), could you verify that the documentation for how to
authenticate as referenced from CONNECTORS-565 seems to work?
Thanks,
Karl
On Mon, Oct 26, 2015 at 12:51 PM, <[email protected]
<mailto:[email protected]>> wrote:
Hi Karl,
It is interesting you ask that as I am just about to set up a fully
functional Sharepoint instance in order to test out other Sharepoint
interactions that I am working on. I would be happy to be a tester
for an upcoming Sharepoint REST API connector.
My background in Enterprise Search has seen me integrate with SP
repositories a number of times so I should hopefully be able to put
any new connector through it's paces!
Paul
-----Original Message-----
From: "Karl Wright" <[email protected] <mailto:[email protected]>>
Sent: Monday, October 26, 2015 12:23pm
To: "[email protected] <mailto:[email protected]>"
<[email protected] <mailto:[email protected]>>
Subject: Re: SharePoint Connector using REST-API
Hi Ruediger,
There's a ticket for this, and people periodically express interest in
doing it, but so far nobody has actually done it.
I'm happy to co-develop it, if there's someone out there who has the
time
and resources (e.g. a working SharePoint instance and some degree of
configuration skill) to try out what I code up in a timely way.
Karl
On Mon, Oct 26, 2015 at 12:16 PM, <[email protected]
<mailto:[email protected]>> wrote:
> Hi all,
>
> since SharePoint 2013 the ASP.NET <http://ASP.NET> (asmx) web
services are listed as
> deprecated API [1]. Microsoft recommends to not use them for new
projects.
>
> Are there any plans or is there any progress in developing a
SharePoint
> Connector using the REST-API [2]?
>
> regards
> -Ruediger
>
> [1]
>
https://msdn.microsoft.com/en-us/library/office/jj164060.aspx#DeprecatedAPIs
> [2] https://msdn.microsoft.com/EN-US/library/office/dn268594.aspx
>
>
