-
Install and configure the Citrix Gateway appliance
-
Deploy Citrix Gateway in a double-hop DMZ
-
Maintain and monitor Citrix Gateway systems
-
Configure DTLS VPN virtual server using SSL VPN virtual server
-
Integrate Citrix Gateway with Citrix products
-
Integrate Citrix Gateway with Citrix Virtual Apps and Desktops
-
Configure settings for your Citrix Endpoint Management Environment
-
Configure load balancing servers for Citrix Endpoint Management
-
Configure load balancing servers for Microsoft Exchange with Email Security Filtering
-
Configure Citrix Endpoint Management NetScaler Connector (XNC) ActiveSync Filtering
-
Allow Access from mobile devices with Citrix Mobile Productivity Apps
-
Configure domain and security token authentication for Citrix Endpoint Management
-
Configure client certificate or client certificate and domain authentication
-
-
Configuring Settings for Your Citrix Endpoint Management Environment
-
Configuring Load Balancing Servers for Citrix Endpoint Management
-
Configuring Load Balancing Servers for Microsoft Exchange with Email Security Filtering
-
Configuring Citrix Endpoint Management NetScaler Connector (XNC) ActiveSync Filtering
-
Allowing Access from Mobile Devices with Citrix Mobile Productivity Apps
-
Configuring Domain and Security Token Authentication for Citrix Endpoint Management
-
Configuring Client Certificate or Client Certificate and Domain Authentication
-
-
-
Configuring a Citrix Gateway application on the Azure portal
-
Configuring Citrix Gateway Virtual Server for Microsoft ADAL Token Authentication
-
Set up Citrix Gateway for using micro VPN with Microsoft Endpoint Manager
-
Citrix Gateway Enabled PCoIP Proxy Support for VMware Horizon View
-
Proxy Auto Configuration for Outbound Proxy support for Citrix Gateway
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configuring Citrix Gateway Virtual Server for Microsoft ADAL Token Authentication
To configure a Citrix Gateway virtual server for monitoring Microsoft ADAL token authentication, you need the following information:
- certEndpoint: The URL of the endpoint that contains the JSON Web Key (JWK) for ADAL token verification.
- Audience: FQDN of the Citrix ADC virtual server to which the app sends the ADAL token.
- Issuer: Name of the AAD issuer. Gets populated by default.
- TenantID: Tenant ID for Azure ADAL registration.
- ClientID: A unique ID given to the Gateway app as part of ADAL registration.
- ClientSecret: A secret key given to the Gateway app as part of ADAL registration.
- ResourceURI: An optional parameter to capture the resource URI. If not configured, Citrix ADC uses Azure commercial resource URI.
Perform the following steps using the command line interface:
-
Create an OAuth action.
add authentication OAuthAction <oauth-action-name> -OAuthType <INTUNE> –clientid <clientID> -clientsecret <client-secret> -audience <audience name> -tenantid <tenantID> -issuer <issuer-name> -userNameField <upn> -certEndpoint <certEndpoint-name> -resourceURI <name of resource URI> <!--NeedCopy-->
-
Create an authentication policy to associate with the newly created OAuth action.
add authentication Policy <policy-name> -rule <true> -action <oauth intune action> <!--NeedCopy-->
-
Bind the newly created OAuth to AuthVS.
bind authentication vserver <auth-vserver> -policy <oauth-intune-policy> -priority 2 -gotoPriorityExpression END <!--NeedCopy-->
-
Create a LoginSchema.
add authentication loginSchema <loginSchemaName> -authenticationSchema <authenticationSchema”location”> add authentication loginSchemaPolicy <loginSchemaPolicyName> -rule true -action <loginSchemaName> <!--NeedCopy-->
-
Bind AuthVS with LoginSchema.
bind authentication vserver <auth-vs> -policy <oauth-pol> -priority 2 -gotoPriorityExpression END <!--NeedCopy-->
-
Add an authentication profile and assign it to a VPN virtual server.
add authnprofile <nfactor-profile-name> -authnvsName <authvserver> set vpn vserver <vserver-name> -authnprofile <nfactor-profile-name> <!--NeedCopy-->
Sample configuration
add authentication OAuthAction tmp-action -OAuthType INTUNE -clientid id 1204 -clientsecret a -audience "[http://hello](http://hello/)" -tenantid xxxx -issuer "[https://hello](https://hello/)" -userNameField upn -certEndpoint https://login.microsoftonline.com/common/discovery/v2.0/keys --resourceURI htpps://api.manage.microsoft.com
add authentication Policy oauth-intune-pol -rule true -action tmp-action
bind authentication vserver auth-vs-for-gw1-intune -policy oauth-pol -priority 2 -gotoPriorityExpression END
add authentication loginSchema oauth-loginschema -authenticationSchema "/nsconfig/loginschema/LoginSchema/OnlyOAuthToken.xml"
add authentication loginSchemaPolicy oauth-loginschema-pol -rule true -action oauth-loginschema`
bind authentication vserver auth-vs-for-gw1-intune -policy oauth-loginschema-pol -priority 2 -gotoPriorityExpression END
add authnprofile nfactor-prof-intune -authnvsName auth-vs-for-gw1-intune
set vpn vserver gw1-intune-authnprofile nfactor-prof-intune
<!--NeedCopy-->
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.