Sergii Vorushylo
Jun 7, 2011
  5637
(1 votes)

EPiServer Connect for SharePoint 2.4 and Virtual Path Provider file check out

The new version of EPiServer Connect for Microsoft SharePoint offers a lot of fixes, mostly related to overcome changes in MOSS 2010 in comparison with MOSS 2007 and to increase overall stability of the module. Also the new version has an improvement for the file check out operation in Virtual Path Provider for SharePoint (VPP SP).

VPP SP can be configured in two security modes: “single user” - when a special SharePoint account is used, and delegation - when CMS users connect to SharePoint with their own credentials.

Single user mode configuration sample:

   1: <add name="SharePointFiles" showInFileManager="true" bypassAccessCheck="false" 
   2:   virtualPath="~/SharePoint/" isMOSS="False" wssSiteUrl="http://vm-sp"
   3:   wssDomainName="" wssLogin="Administrator" wssPassword="p@ss1word" useImpersonation="false" 
   4:   virtualName="SharePoint" customFileSummary="~/WSSFileSummary.config" 
   5:   useCache="True" cacheExpirationTime="30" 
   6:   type="EPiServer.VirtualPathWssProvider.VirtualPathWssProvider,EPiServer.VirtualPathWssProvider" 
   7:   wssRootFolder="Shared Documents" /> 

If VPP SP is configured in a “single user” authentication mode all users actions in EPiServer CMS file manager are executed on the SharePoint side on behalf of the user specified in VPP SP configuration (see line 3 in the sample). The main advantage of the “single user” mode is that it is much easier to configure. In most cases it works fine, except Check Out and Check In operations. In the previous version a file, checked out by any user in CMS file manager, is displayed as checked out by the user specified in VPP SP configuration:

CheckOutUser

In the new version we implemented a better support of this operations. When user performs Check Out operation on a file in VPP SP the special record is made in EPiServer CMS database (using Dynamic Data Store). Information from this record is used to display proper value of the “Checked Out By” field and enables Check In or Cancel Check Out operations only for the user who actually checked out the file or administrators.

CheckOutUserProper

This workaround makes operations with file versions in VPP SP more convenient. However, on the SharePoint side everything looks the same as before since the files in fact, checked out in SharePoint by the user specified in VPP SP configuration. If that solution does not fit your needs you can use delegation – in that case all file operations are executed as if the user is on SharePoint site.

Jun 07, 2011

Comments

Please login to comment.
Latest blogs
Plug-in manager is back in CMS 12

Plug-in manager is back in the UI, what is it and how can i use it?

Luc Gosso (MVP) | Oct 6, 2022 | Syndicated blog

Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog