-
Notifications
You must be signed in to change notification settings - Fork 107
SPWebAppPolicy
Parameter | Attribute | DataType | Description | Allowed Values |
---|---|---|---|---|
WebAppUrl | Key | String | The URL of the web application | |
Members | Write | MSFT_SPWebPolicyPermissions[] | Exact list of accounts that will have to get Web Policy permissions | |
MembersToInclude | Write | MSFT_SPWebPolicyPermissions[] | List of all accounts that must be in the Web Policy group | |
MembersToExclude | Write | MSFT_SPWebPolicyPermissions[] | List of all accounts that are not allowed to have any Web Policy permissions | |
SetCacheAccountsPolicy | Write | Boolean | Include the Cache Accounts in the policy or not |
Parameter | Attribute | DataType | Description | Allowed Values |
---|---|---|---|---|
Username | Required | String | Name of the account | |
PermissionLevel | Write | StringArray[] | Permission level of the account |
Deny All , Deny Write , Full Read , Full Control
|
IdentityType | Write | String | Identity type for this entry, either claims or native. If not specified it will default to whatever mode the web application is in. |
Claims , Native
|
ActAsSystemAccount | Write | Boolean | Specifies if the account is allowed to act as a system account |
Type: Distributed Requires CredSSP: No
This resource is used to set the User Policies for web applications. The usernames can be either specified in Classic or Claims format, both will be accepted. There are a number of approaches to how this can be implemented. The "Members" property will set a specific list of members for the group, making sure that every user/group in the list is in the group and all others that are members and who are not in this list will be removed. The "MembersToInclude" and "MembersToExclude" properties will allow you to control a specific set of users to add or remove, without changing any other members that are in the group already that may not be specified here, allowing for some manual management outside of this configuration resource.
Requirements: At least one of the Members, MemberToInclude or MembersToExclude properties needs to be specified. Do not combine the Members property with the MemberToInclude and MembersToExclude properties. Do not set the ActAsSystemAccount property to $true without setting the permission level to
This example sets the specific web app policy for the specified web app to match the provided list below.
Configuration Example
{
param
(
[Parameter(Mandatory = $true)]
[PSCredential]
$SetupAccount
)
Import-DscResource -ModuleName SharePointDsc
node localhost
{
SPWebAppPolicy WebAppPolicy
{
WebAppUrl = "http://sharepoint.contoso.com"
Members = @(
MSFT_SPWebPolicyPermissions {
Username = "contoso\user1"
PermissionLevel = "Full Control"
ActAsSystemAccount = $true
}
MSFT_SPWebPolicyPermissions {
Username = "contoso\Group 1"
PermissionLevel = "Full Read"
IdentityType = "Claims"
}
)
PsDscRunAsCredential = $SetupAccount
}
}
}
This example shows how to include specific members while excluding other members from the policy of the web app.
Configuration Example
{
param
(
[Parameter(Mandatory = $true)]
[PSCredential]
$SetupAccount
)
Import-DscResource -ModuleName SharePointDsc
node localhost
{
SPWebAppPolicy WebAppPolicy
{
WebAppUrl = "http://sharepoint.contoso.com"
MembersToInclude = @(
@(MSFT_SPWebPolicyPermissions {
Username = "contoso\user1"
PermissionLevel = "Full Control"
})
@(MSFT_SPWebPolicyPermissions {
Username = "contoso\user2"
PermissionLevel = "Full Read"
})
)
MembersToExclude = @(
@(MSFT_SPWebPolicyPermissions {
Username = "contoso\user3"
})
)
SetCacheAccountsPolicy = $true
PsDscRunAsCredential = $SetupAccount
}
}
}
- Home
- Getting Started
- Pre-requisites
- Installing the module
- Exporting SharePoint Configuration
- Creating Configuration Files
- Pre-created Examples
- Creating an Azure development environment
- Understanding Resources & Syntax
- Remote PowerShell Authentication
- Contributing to SharePointDsc
- Other useful modules for SharePoint DSC configurations