November Happy Hour will be moved to Thursday December 5th.

Integration between CMS 6 and Sharepoint 2010

Vote:
 

Hi everyone!

So we're doing an intranet with CMS 6 and Community 4 where we want to use Sharepoint 2010 for filehandling. The idea is to authenticate users on both platforms through a shared Active Directory in order avoid multiple user directories, and to keep the user in CMS 6 as far as it's possible in order to avoid them having to learn and use multiple interfaces.

I've been looking into the Sharepoint Connector, but it would be interesting to get some input of someone who has implemented in a live project. Does it work well enough with EPiServer that the editor never has to know Sharepoint is actually behind the scenes, or does it require manual intervention, for instance when setting user restrictions on files and folders?

The user restrictions in general is another question, EPiServer doesn't add that much user metadata on top of the AD authentication, but both Sharepoint and Community does add a bit of it, and i'm pretty sure we'll want to sync this data in some way along the way. Same is true for file metadata, tags and categories and stuff. The Connector probably can't be used for this (?), but is there a good way to sync this, has it been done?

We also want to let the users search both CMS pages, Community stuff, and Sharepoint files. The idea is to use the new Community search engine for CMS/Community things, and the Sharepoint Searchengine through webservice for the SP stuff, then add a wrapper on top of that to present a unified searchresult. Of course here as well we have a bit of a problem with, for instance, user restrictions, how to apply that and make sure only the correct files are returned. Anyone have experience with doing this?

Grateful for any insights!

 

#46470
Dec 14, 2010 13:32
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.