.png)
Set-SPSecureStoreDefaultProvider
Published: July 16, 2012
Applies to: SharePoint Foundation 2013 | SharePoint Server 2013 Enterprise
Updates the secure store provider.
Set-SPSecureStoreDefaultProvider -Type <Type> [-AssignmentCollection <SPAssignmentCollection>]
Parameters
| Parameter | Required | Type | Description | ||
|---|---|---|---|---|---|
| Type | Required | System.Type | Specifies the provider type. The type must be loaded in memory. The type must be a secure store provider type enclosed in square brackets; for example, [Reflection.Assembly]. | ||
| AssignmentCollection | Optional | Microsoft.SharePoint.PowerShell.SPAssignmentCollection | Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
|
Note: Detailed Description
The Set-SPSecureStoreDefaultProvider cmdlet sets or replaces the secure store provider. To register a third-party secure store, implement the ISecureStoreProvider interface. With the interface defined, place the DLL file in the global assembly cache, and then load the DLL and load the type, as shown in the example. You can then set the secure store provider.
Input Types
Return Types
------------------EXAMPLE------------------
[Reflection.Assembly]::LoadFrom("C:\ContosoFolder\contosoSecureStore.dll")
$type = [Contoso.SecureStore.ContosoSecureStoreProvider]
Set-SPSecureStoreDefaultProvider –Type $type
This example sets the custom implemented secure store provider.
Change History
| Date | Description |
|---|---|
| July 16, 2012 | Initial publication |
