Default Value for Secure Store Implementation Field

When you import a BDC model into Central Administration in SharePoint 2013, you often need to configure it to use a Secure Store Target Application. This is straightforward to an extent:
  1. Browse the external systems in your BDC service application.
  2. Click through to the settings of the external system that corresponds to your BDC model.
  3. Select an appropriate Authentication Mode for your Secure Store Target Application (Impersonate Windows Identity or Impersonate Custom Identity).
  4. Provide the target application ID for your secure store target application.
The tricky bit is that SharePoint expects you to provide a value for Secure Store Implementation. If you've changed the authentication mode from User's Identity or BDC Identity, this field will be blank:






















What you actually need to type in this Secure Store Implementation field is the fully-qualified type name for the secure store provider. Unless you've built your own secure store provider (in which case you're the ultimate SharePoint guru), this value will always be the same:

Microsoft.Office.SecureStoreService.Server.SecureStoreProvider, Microsoft.Office.SecureStoreService, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c

Copy that typename into the Secure Store Implementation field and you should be good to go. I've had to hunt this value down on several occasions, so hopefully having it here for easy copy-and-paste will come in useful.

Comments

Post a comment

Popular posts from this blog

Server-side activities have been updated

Image
If you use SharePoint Designer 2013 to build workflows, there's a fair chance you'll have come across the following error message:
Server-side activities have been updated. You need to restart SharePoint Designer to use the updated version of activities.  Needless to say, restarting SharePoint Designer rarely makes the error go away. The usual advice is:

Approach 1: Clear the cache folders
See for example How to Clear Your SharePoint Designer 2010/2013 Cache. If you've just deployed some custom workflow activities to your site, this will probably solve your problem (and you should clear the cache folders every time you deploy custom activities). If the error occurs spontaneously, this approach often won't help.

Approach 2: Reinstall SharePoint Designer
This might work if you've got a preview version of SharePoint Designer installed. If not, it's unlikely to help. It didn't work for me, and it didn't work for countless others on the forums.

Approach 3: Insta…
Read more

The target principal name is incorrect. Cannot generate SSPI context.

Image
Today's problem occured after I restarted a Hyper-V based SharePoint 2013 farm (Windows Server 2012, one SharePoint 2013 machine, one SQL Server 2012 machine, one DC). I fired up Central Administration and was hit with the following error:

Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.

The target principal name is incorrect. Cannot generate SSPI context.

After checking the obvious things - testing connectivity to the DB server, checking the SQL service was running, verifying permissions, etc - I initially figured this was an issue with my Hyper-V snapshots being out of sync, so I ran the SharePoint Products Configuration Wizard. This hit me with the following error:

Failed to detect if this server is joined to a server farm. Possible reasons for this failure could be that you no longer have appropriate permissions to the server farm, the database server hosting the server farm is unresponsive, the configuration database is inaccessib…
Read more

Versioning SharePoint Framework Packages

Image
TL;DR: Package versioning in SPFx web parts is confusing. Your sites will notify you that an upgrade is available, but will automatically use the latest version of your code regardless.

 Package versioning behaviour in the SharePoint Framework is currently a little idiosyncratic, and it recently caused us a few headaches. It seems that from a versioning perspective SharePoint (incorrectly) expects the SPFx packages to behave like SharePoint Add-ins. In this post I'll run through some of the issues we encountered and how we worked through it.

Context You can version an SPFx package in three places:

The SharePoint package manifest, in the package-solution.json file.The component manifests, in one or more .manifest.json files.The NPM package manifest, in the package.json file.
In this post we're looking at the SharePoint package manifest (package-solution.json) as this is the version number that SharePoint reads and propagates when you deploy a package to the App Catalog.

The Probl…
Read more