SharePoint 2013

Applies to: SharePoint Foundation 2013, SharePoint Server 2013 Enterprise

Topic Last Modified: 2015-03-09

Returns an authentication provider.

Get-SPAuthenticationProvider [[-Identity] <SPAuthenticationProviderPipeBind>] [-WebApplication] <SPWebApplicationPipeBind> [-Zone] <Default | Intranet | Internet | Custom | Extranet> [-AssignmentCollection <SPAssignmentCollection>]

The Get-SPAuthenticationProvider cmdlet returns an authentication provider on a specified Web application zone. The following are the standard authentication providers available for SharePoint 2010 Products: NTLM, Classic NTLM, Negotiate, and Classic Negotiate.

SharePoint Management Shell


Parameter Required Type Description




Specifies the authentication provider to get.

The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a SharePoint authentication provider (for example, NTLM); or an instance of a valid SPAuthenticationProvider object.




Returns the content databases for the specified Web application.

The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint Web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object.




Specifies the Web application zone or zones for which to return the authentication provider.

The type must be any one of the valid zones: Default, Intranet, Internet, Extranet, or Custom.




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.

When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.

-----------------EXAMPLE 1-----------------

New-SPWebApplication -AuthenticationProvider (Get-SPAuthenticationProvider "LiveID STS")

This example registers the LiveID STS authentication provider for the new Web application.

-----------------EXAMPLE 2-----------------

New-SPWebApplication -AuthenticationProvider (New-SPAuthenticationProvider -ASPNetMembershipProvider "myMembershipProvider" -ASPNetRoleProvider "myRoleProvider")

This example registers ASPNet for the new Web application. Note that ASPNET memberships are not persisted and must be re-created every use.

-----------------EXAMPLE 3-----------------

New-SPWebApplication -AuthenticationProvider (Get-SPAuthenticationProvider "NTLM")

This example registers the NTLM authentication provider for the new Web application. This command is equivalent to the command New-SPWebApplication; NTLM is default authentication provider.

-----------------EXAMPLE 4-----------------

$ip = @( (Get-SPAuthenticationProvider "LiveID STS"), (New-SPAuthenticationProvider -ASPNetMembershipProvider "myMembershipProvider" -ASPNetRoleProvider "myRoleProvider"), (Get-SPAuthenticationProvider "NTLM")) )New-SPWebApplication -AuthenticationProvider $ip

This example registers the NTLM, ASPNet, and LiveID STS authentication providers for the new Web application.

-----------------EXAMPLE 5-----------------

New-SPWebApplication -AuthenticationProvider (Get-SPAuthenticationProvider "Legacy NTLM")

This example registers the Legacy NTLM authentication provider for the new Web application.