Add-AdfsNonClaimsAwareRelyingPartyTrust

Add-AdfsNonClaimsAwareRelyingPartyTrust

Adds a relying party trust that represents a non-claims-aware web application or service to the Federation Service.

Syntax

Parameter Set: Default
Add-AdfsNonClaimsAwareRelyingPartyTrust [-Name] <String> [-Identifier] <String[]> [-AdditionalAuthenticationRules <String> ] [-AdditionalAuthenticationRulesFile <String> ] [-AlwaysRequireAuthentication] [-Enabled <Boolean> ] [-IssuanceAuthorizationRules <String> ] [-IssuanceAuthorizationRulesFile <String> ] [-Notes <String> ] [-PassThru] [-Confirm] [-WhatIf] [ <CommonParameters>]

Detailed Description

The Add-AdfsNonClaimsAwareRelyingPartyTrust cmdlet creates a relying party trust for web applications or services that do not rely directly on Active Directory Federation Services (AD FS) to issue tokens, but instead rely on a third party that accesses such tokens and transforms them into what applications understand. A non-claims-aware relying party trust is useful for defining authentication and authorization policies for web applications and services that do not rely on AD FS tokens. The Web Application Proxy requests such tokens for preauthentication to web applications or services that have corresponding non-claims-aware relying party trusts for requests that come from outside the network through the proxy.

Parameters

-AdditionalAuthenticationRules<String>

Specifies rules for additional authentication on the relying party. For more information about the claims language for rules, see Understanding Claim Rule Language in AD FS 2.0 & Higher on TechNet.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-AdditionalAuthenticationRulesFile<String>

Specifies the file that contains all the rules for additional authentication for the relying party.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-AlwaysRequireAuthentication

Indicates that access requires authentication, even if this relying party has previously authenticated credentials for access. Specify this parameter to require users to always supply credentials to access sensitive resources.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Enabled<Boolean>

Indicates whether to enable this relying party trust. Specify a value of $True for this parameter to allow authentication and authorization to the relying party.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Identifier<String[]>

Specifies an array of unique identifiers for the non-claims-aware relying party trust. No other trust can use an identifier from this list. As common practice, you can use Uniform Resource Identifiers (URIs) as unique identifiers for a relying party trust, or you can use any string.

Aliases

none

Required?

true

Position?

2

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-IssuanceAuthorizationRules<String>

Specifies the authorization rules for issuing claims to the relying party.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

-IssuanceAuthorizationRulesFile<String>

Specifies the file that contains the authorization rules for issuing claims to the relying party.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Name<String>

Specifies a name. The cmdlet adds the Web Application Proxy relying party trust that has the display name that you specify.

Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Notes<String>

Specifies notes for the relying party trust. Use this parameter to store information such as owners and contacts when you manage a large number of applications.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-PassThru

Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Confirm

Prompts you for confirmation before running the cmdlet.

Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.

Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

Examples

Example 1: Add a non-claims-aware relying party trust for an application

This command adds a non-claims-aware relying party trust for the application named ExpenseReport and allows all authenticated users to access this application through the Web Application Proxy.

PS C:\> Add-AdfsNonClaimsAwareRelyingPartyTrust -Name 'ExpenseReport' -Identifier 'http://contosoexpense/' -IssuanceAuthorizationRules '=>issue(Type = "https://schemas.microsoft.com/authorization/claims/permit", Value = "true");'

Example 2: Add a non-claims-aware relying party trust that restricts access to an application

This command adds a non-claims-aware relying party trust for the application named ExpenseReport and restricts access to this application, through the Web Application Proxy, to only users from their workplace-joined devices.

PS C:\> Add-AdfsNonClaimsAwareRelyingPartyTrust -Name 'ExpenseReport' -Identifier 'http://contosoexpense/' -IssuanceAuthorizationRules 'c:[type=="https://schemas.microsoft.com/2012/01/devicecontext/claims/isregistereduser"]=>issue(Type = "https://schemas.microsoft.com/authorization/claims/permit", Value = "true");'

Get-AdfsNonClaimsAwareRelyingPartyTrust

Set-AdfsNonClaimsAwareRelyingPartyTrust

Enable-AdfsNonClaimsAwareRelyingPartyTrust

Disable-AdfsNonClaimsAwareRelyingPartyTrust

Remove-AdfsNonClaimsAwareRelyingPartyTrust