Amend the Owstimer.exe.config to support DocRead under FBA

If you choose to use a different authentication mechanism such as FBA that requires a ‘Role’ and ‘Membership’ provider specified in your web.config then you will also need to copy these entries to your owstimer.exe.config file.

Here’s an example of a working owstimer.exe.config file that is set-up to use Extradium. (Extradium is an identity management solution that allows you to make your SharePoint accessible externally and works really well with DocRead). If you don’t do this, then the DocRead timer jobs will not be able to access the FBA database causing the SharePoint API to return empty groups. This will result in tasks being removed, so it’s vitally important you copy the entries from your web.config.

Example :

<?xml version="1.0" encoding="utf-8" ?>
 <startup useLegacyV2RuntimeActivationPolicy="true">
 <supportedRuntime version="v4.0.30319" />
 <NetFx40_LegacySecurityPolicy enabled="true" />
 <appDomainManagerAssembly value="Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
 <appDomainManagerType value="Microsoft.SharePoint.SPAppDomainManager" />
 <membership defaultProvider="i">
 <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
 <add name="ext" type="RioLinx.Extradium.Providers.ExtradiumMembershipProvider, RioLinx.Extradium.Providers, Version=, Culture=neutral, PublicKeyToken=ee2f606d34db8cb1" />
 <roleManager defaultProvider="c" enabled="true" cacheRolesInCookie="false">
 <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
 <add name="extg" type="RioLinx.Extradium.Providers.ExtradiumRoleProvider, RioLinx.Extradium.Providers, Version=, Culture=neutral, PublicKeyToken=ee2f606d34db8cb1" />