Get-AdfsWebApplicationProxyRelyingPartyTrust
Gets the relying party trust object for the Web Application Proxy.
Syntax
Get-AdfsWebApplicationProxyRelyingPartyTrust []
Description
The Get-AdfsWebApplicationProxyRelyingPartyTrust cmdlet gets the Web Application Proxy relying party trust object for the proxy.
The Web Application Proxy relying party trust is useful to manage global network access from outside the corporate network. By setting authentication and authorization policies, an administrator can restrict access to internal web applications and services that are published through the Web Application Proxy.
Examples
Example 1: Get the relying party trust object
PS C:\> Get-AdfsWebApplicationProxyRelyingPartyTrust
AlwaysRequireAuthentication : False
Enabled : True
Identifier : {urn:AppProxy:com}
IssuanceAuthorizationRules : @RuleTemplate="AllowAllAuthzRule" => issue(Type = "http://schemas.contoso.com/authorization/claims/permit", Value="true");
IssuanceTransformRules : @RuleTemplate="PassThroughClaims"
@RuleName="Pass Through Application Identifier"
c:[Type == "http://schemas.contoso.com/2012/01/requestcontext/claims/relyingpartytrustid"] => issue(claim = c);
@RuleTemplate="PassThroughClaims"
@RuleName="Pass Through Device Registration Identifier"
c:[Type == "http://schemas.contoso.com/2012/01/devicecontext/claims/registrationid"] => issue(claim = c);
@RuleTemplate="PassThroughClaims"
@RuleName="Pass Through UPN"
c:[Type == "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn"] => issue(claim = c);
@RuleTemplate="PassThroughClaims"
@RuleName="Pass Through Activity ID"
c:[Type == "http://schemas.contoso.com/2012/01/requestcontext/claims/client-request-id"] => issue(claim = c);
AdditionalAuthenticationRules :
Name : urn:AppProxy:com
NotBeforeSkew : 0
Notes :
RelyingPartyType : WebApplicationProxy
TokenLifetime : 0
This command gets the Web Application Proxy relying party trust object. The command displays authentication and authorization rules added previously.
Related Links
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기