New-NetIPsecPhase2AuthSet
Creates a phase 2 authentication set that specifies the methods offered for second user authentication during IPsec negotiations.
Syntax
New-NetIPsecPhase2AuthSet
[-PolicyStore <String>]
[-GPOSession <String>]
[-Name <String>]
-DisplayName <String>
[-Description <String>]
[-Group <String>]
-Proposal <CimInstance[]>
[-Default]
[-CimSession <CimSession[]>]
[-ThrottleLimit <Int32>]
[-AsJob]
[-WhatIf]
[-Confirm]
[<CommonParameters>] Description
The New-NetIPsecPhase1AuthSet cmdlet creates a set that specifies the computer authentication methods, usually for the computer to use during IPsec negotiations. The first phase of authentication is typically a computer authentication method such as Kerberos v5, certificate, or pre-shared key (PSK) authentication.
A phase 1 authentication set is contains an ordered list of computer authentication proposals. Each proposal in the set specifies the authentication methods to propose. A proposal is created by running the New-NetIPsecAuthProposal cmdlet. During the main mode negotiation, the first proposal that both peers have in common will be used for mutual authentication. The main mode exchange will use the first proposal that the peers have in common. A NetIPsecPhase1AuthSet object and a NetIPsecMainModeCryptoSet object are associated to a NetIPsecMainModeRule object to provide all the necessary security association (SA) parameters for customized main mode negotiations. When the negotiation is successful, a network IPsec main mode SA is created. Use the Get-NetIPsecMainModeSA cmdlet to monitor the SAs that are created.
The default computer authentication set is used with all IPsec rules as specified by the Default parameter at creation time. Additional authentication sets can be used with IPsec main mode rules for fully customized main mode negotiations.
The newly created authentication set can be configured associated with one or more IPsec rules using the main mode or an IPsec rule with the Set-NetIPsecRule and cmdlet or the Set-NetIPsecMainModeRule cmdlets.
This cmdlet creates a set that specifies the authentication methods, usually for user, to use during IPsec negotiations. The second phase of authentication is typically a user authentication method, such as Kerberos v5, certificate, or PSK authentication. The New-NetIPsecPhase1AuthSet cmdlet creates a set of authentication methods to use during IPsec negotiations. The first phase of authentication is typically a computer authentication method such as Kerberos v5, certificate, or PSK authentication.
A phase 1 authentication set contains an ordered list of authentication proposals. A proposal is created by running the New-NetIPsecAuthProposal cmdlet. During the main mode negotiation, the first proposal that both peers have in common will be used for mutual authentication. A NetIPsecPhase1AuthSet object and a NetIPsecMainModeCryptoSet object provide all of the necessary SA parameters for a NetIPsecMainModeRule. Use the Get-NetIPsecMainModeSA cmdlet to monitor the SAs that are created.
The default computer authentication set is used with all IPsec rules as specified by the Default parameter at creation time. Additional authentication sets can be used with IPsec main mode rules for fully customized main mode negotiations.
The newly created authentication set can be associated with one or more IPsec rules using the Set-NetIPsecRule and Set-NetIPsecMainModeRule cmdlets.
A phase 2 authentication set is an ordered list of user authentication proposals. Each proposal in the set specifies the authentication methods to propose. A proposal is created by the New-NetIPsecAuthProposal cmdlet. The phase 2 authentication set is configured to an IPsec rule.
A second authentication cannot be specified in an IPsec rule when a PSK is in the first authentication methods list, with the PhaseAuthSet object.
The user authentication set can be configured to an existing IPsec rule with the Set-NetIPsecRule cmdlet. The default user authentication set is used with all IPsec rules, and specified with Default parameter at creation time.
Examples
EXAMPLE 1
PS C:\>$mkerbauthprop = New-NetIPsecAuthProposal -Machine -Kerberos
PS C:\>$mntlmauthprop = New-NetIPsecAuthProposal -Machine -NTLM
PS C:\>$p1Auth = New-NetIPsecPhase1AuthSet -DisplayName "First Machine Auth" -Proposal $mkerbauthprop,$mntlmauthprop
PS C:\>$ukerbauthprop = New-NetIPsecAuthProposal -User -Kerberos
PS C:\>$unentlmauthprop = New-NetIPsecAuthProposal -User -NTLM
PS C:\>$anonyauthprop = New-NetIPsecAuthProposal -Anonymous
PS C:\>$p2Auth = New-NetIPsecPhase2AuthSet -DisplayName "Second User Auth" -Proposal $ukerbauthprop,$unentlmauthprop,$anonyauthprop
PS C:\>New-NetIPSecRule -DisplayName "Authenticate Both Computer and User" -InboundSecurity Require -OutboundSecurity Require -Phase1AuthSet $p1Auth.Name -Phase2AuthSet $p2Auth.NameThis example creates a rule that requires a first, or computer, authentication and attempts an optional second, or user, authentication.
Parameters
-AsJob
Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete.
| Type: | SwitchParameter |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-CimSession
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
| Type: | CimSession[] |
| Aliases: | Session |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Confirm
Prompts you for confirmation before running the cmdlet.
| Type: | SwitchParameter |
| Aliases: | cf |
| Position: | Named |
| Default value: | False |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Default
Specifies the customized parameters for overriding the defaults for main mode encryption, making it the new default setting for encryption. For the default Phase2AuthSet object, the default Name parameter value is {E5A5D32A-4BCE-4e4d-B07F-4AB1BA7E5FE4}. To retrieve default settings, query by using the default Name parameter value. To specify a different default cryptographic set, delete the current default set and use the Rename-NetIPsecPhase2AuthSet cmdlet to specify the default set with {E5A5D32A-4BCE-4e4d-B07F-4AB1BA7E5FE4}.
| Type: | SwitchParameter |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Description
Specifies that matching IPsec rules of the indicated description are created. Wildcard characters are accepted. This parameter provides information about the firewall rule. This parameter specifies the localized, user-facing description of the IPsec rule.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-DisplayName
Specifies that only matching firewall rules of the indicated display name are created. Wildcard characters are accepted. Specifies the localized, user-facing name of the firewall rule being created. When creating a rule this parameter is required. This parameter value is locale-dependent. If the object is not modified, this parameter value may change in certain circumstances. When writing scripts in multi-lingual environments, the Name parameter should be used instead, where the default value is a randomly assigned value. This parameter cannot be set to All.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-GPOSession
Specifies the network GPO from which to retrieve the rules to be created. This parameter is used in the same way as the PolicyStore parameter. When modifying GPOs in Windows PowerShell®, each change to a GPO requires the entire GPO to be loaded, modified, and saved back. On a busy Domain Controller (DC), this can be a slow and resource-heavy operation. A GPO Session loads a domain GPO onto the local computer and makes all changes in a batch, before saving it back. This reduces the load on the DC and speeds up the Windows PowerShell cmdlets. To load a GPO Session, use the Open-NetGPO cmdlet. To save a GPO Session, use the Save-NetGPO cmdlet.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Group
Specifies that only matching firewall rules of the indicated group association are created. Wildcard characters are accepted. This parameter specifies the source string for the DisplayGroup parameter. If the DisplayGroup parameter value is a localizable string, then this parameter contains an indirect string. Rule groups can be used to organize rules by influence and allows batch rule modifications. Using the Set-NetIPsecRule cmdlets, if the group name is specified for a set of rules or sets, then all of the rules or sets in that group receive the same set of modifications. It is good practice to specify this parameter value with a universal and world-ready indirect @FirewallAPI name. The DisplayGroup parameter cannot be specified upon object creation using the New-NetIPsecRule cmdlet, but can be modified using dot-notation and the Set-NetIPsecRule cmdlet.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Name
Specifies that only matching main mode cryptographic sets of the indicated name are created. Wildcard characters are accepted. This parameter acts just like a filename, in that only one rule with a given name may exist in a policy store at a time. During group policy processing and policy merge, rules that have the same name but come from multiple stores being merged, will overwrite one another so that only one exists. This overwriting behavior is desirable if the rules serve the same purpose. For instance, all of the firewall rules have specific names, so if an administrator can copy these rules to a GPO, and the rules will override the local versions on a local computer. GPOs can have precedence. So, if an administrator has a different or more specific rule the same name in a higher-precedence GPO, then it overrides other rules that exist. The default value is a randomly assigned value.When you want to override the defaults for main mode encryption, specify the customized parameters and set this parameter value, making this parameter the new default setting for encryption.
| Type: | String |
| Aliases: | ID |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-PolicyStore
Specifies the policy store from which to retrieve the sets to be created. A policy store is a container for firewall and IPsec policy. The acceptable values for this parameter are:
- PersistentStore: Sometimes called static rules, this store contains the persistent policy for the local computer. This policy is not from GPOs, and has been created manually or programmatically, during application installation, on the computer. Rules created in this store are attached to the ActiveStore and activated on the computer immediately.
- ActiveStore: This store contains the currently active policy, which is the sum of all policy stores that apply to the computer.
This is the resultant set of policy (RSOP) for the local computer (the sum of all GPOs that apply to the computer), and the local stores (the PersistentStore, the Static Windows Service Hardening (WSH), and the Configurable WSH).
---- GPOs are also policy stores.
Computer GPOs can be specified as follows.
------
-PolicyStore hostname. ---- Active Directory GPOs can be specified as follows. -------PolicyStore domain.fqdn.com\GPO_Friendly_Namedomain.fqdn.comGPO_Friendly_Name. ------ Such as the following. ---------PolicyStore localhost---------PolicyStore corp.contoso.com\FirewallPolicy---- Active Directory GPOs can be created using the New-GPO cmdlet or the Group Policy Management Console. - RSOP: This read-only store contains the sum of all GPOs applied to the local computer.
- SystemDefaults: This read-only store contains the default state of firewall rules that ship with Windows Server® 2012.
- StaticServiceStore: This read-only store contains all the service restrictions that ship with Windows. Optional and product-dependent features are considered part of Windows Server 2012 for the purposes of WFAS.
- ConfigurableServiceStore: This read-write store contains all the service restrictions that are added for third-party services. In addition, network isolation rules that are created for Windows Store application containers will appear in this policy store. The default value is PersistentStore. The Set-NetIPsecMainModeCryptoSet cmdlet cannot be used to add an object to a policy store. An object can only be added to a policy store at creation time with the Copy-NetIPsecMainModeCryptoSet cmdlet or with this cmdlet.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Proposal
Associates the specified cryptographic proposal to the corresponding cryptographic set to be used in main mode negotiations. Separate multiple entries with a comma.
| Type: | CimInstance[] |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-ThrottleLimit
Specifies the maximum number of concurrent operations that can be established to run the cmdlet.
If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer.
The throttle limit applies only to the current cmdlet, not to the session or to the computer.
| Type: | Int32 |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
| Type: | SwitchParameter |
| Aliases: | wi |
| Position: | Named |
| Default value: | False |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
Inputs
None
Outputs
The Microsoft.Management.Infrastructure.CimInstance object is a wrapper class that displays Windows Management Instrumentation (WMI) objects.
The path after the pound sign (#) provides the namespace and class name for the underlying WMI object.