-
Install, set up, upgrade, and uninstall
-
Configure authentication and delegation
-
Federated Authentication Service configuration
-
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!
Federated Authentication Service Configuration
When using authentication methods such as SAML, where the user does not enter their credentials directly into Citrix Workspace app, by default it is not possible to single sign-on into VDAs. In these cases, you can use Federated Authentication Service (FAS) to provide single sign-on to VDAs using certificate authentication.
To use FAS with StoreFront, you must configure StoreFront using the PowerShell SDK. Use Set-STFStoreLaunchOptions to set the VDA logon data logon provider to FASLogonDataProvider
.
By default, StoreFront selects the FAS server at launch. You can change this so that StoreFront selects the FAS server at login. This has the advantage that it avoid delays that can occur at launch, particularly if a FAS server is unavailable so it has to try multiple FAS servers. However it has the disadvantage that if the FAS server becomes unavailable between login and launch then the launch either fails or falls back to username and password authentication (see FAS server unavailability). To configure the behavior, run PowerShell cmdlet Set-STFClaimsFactoryNames with parameter ClaimsFactoryName
. To choose the FAS server at login, set it to FASClaimsFactory
. To restore the default behavior and choose a FAS server at launch, set it to standardClaimsFactory
.
For example to enable FAS for a store and select the server at login:
$store = Get-STFStoreService -VirtualPath [VirtualPath]
$auth = Get-STFAuthenticationService -StoreService $store
Set-STFStoreLaunchOptions -StoreService $store -VdaLogonDataProvider "FASLogonDataProvider"
Set-STFClaimsFactoryNames -AuthenticationService $auth -ClaimsFactoryName "FASClaimsFactory"
<!--NeedCopy-->
To disable FAS for a store:
$store = Get-STFStoreService -VirtualPath [VirtualPath]
$auth = Get-STFAuthenticationService -StoreService $store
Set-STFStoreLaunchOptions -StoreService $store -VdaLogonDataProvider ""
Set-STFClaimsFactoryNames -AuthenticationService $auth -ClaimsFactoryName "standardClaimsFactory"
<!--NeedCopy-->
Substitute [VirtualPath]
for the appropriate virtual path, e.g. /Citrix/Store
.
To configure the list of FAS servers and other settings you must use Group policy. For more details see FAS documentation.
FAS server unavailability
If the FAS server is unavailable the launch fails by default. However, you can configure StoreFront such that if the FAS server is unavailable, users can sign on to the VDA by entering their credentials. To change the configuration use Powershell cmdlet Set-STFStoreLaunchOptions with parameter FederatedAuthenticationServiceFailover
. For example to enable fail over for a store:
$storeService = Get-STFStoreService -VirtualPath [VirtualPath]
Set-STFStoreLaunchOptions $storeService -FederatedAuthenticationServiceFailover $True
<!--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 I DO NOT AGREE to exit.