{"id":1634,"date":"2017-10-18T05:30:00","date_gmt":"2017-10-18T05:30:00","guid":{"rendered":"http:\/\/neu.koetzingit.de\/ein-blick-auf-citrix-federated-authentication-service-fas\/"},"modified":"2026-06-02T13:32:49","modified_gmt":"2026-06-02T13:32:49","slug":"ein-blick-auf-citrix-federated-authentication-service-fas","status":"publish","type":"post","link":"https:\/\/www.koetzingit.de\/en\/ein-blick-auf-citrix-federated-authentication-service-fas\/","title":{"rendered":"An Overview of Citrix Federated Authentication Service (FAS)"},"content":{"rendered":"

K<\/span>Recently, one of my clients gave me a problem to solve: \u201eCan we authenticate with the Netscaler Gateway using only a username and security token, from a not a domain member<\/strong> and then access to a full Have you received a Citrix ICA session?<\/strong>\u201e<\/p>\n

This is exactly where the Citrix Federated Authentication Service\u00a0<\/strong>To the rescue!<\/p>\n

<\/p>\n

The customer wants employees to be able to work without passwords, which is why the company uses only smart cards with all domain members. The company devices have no problem accessing the internal network from outside the company. But what about personal devices<\/strong>? In this case, users receive a security token and nothing else. In the past, users had to enter their password at least once in the web interface and then save it.<\/p>\n

In my opinion, this is a good example, and I believe that other Citrix customers have the same or similar requirements. Before I get back to the use cases, let\u2019s first take a look at how the\u00a0Citrix Federated Authentication Service<\/strong>\u00a0throw.<\/p>\n

\u00a0<\/p>\n

Citrix Federated Authentication Service<\/span><\/h3>\n

To make things easier to understand, I'll keep the explanations simple. FAS is a Windows service that Smart Card Class Certificates<\/strong>\u00a0(vSmartCards) on behalf of the Active Directory user. To do this, the service must be authorized by your own internal private certificate authority (CA). The Federated Authentication Service primarily interacts with Citrix StoreFront, although other components such as Netscaler, DDC, and VDA are also involved but are not as critical. The created vSmartCard is then sent to the target VDA server, just as the NFuse ticket was previously. Since FAS holds all private keys for the created user vSmartCards, the system must be secured with restricted access, even for administrators.<\/p>\n

\u00a0<\/p>\n

FAS Setup<\/span><\/h3>\n

FAS has been part of XenApp\/XenDesktop Media since version 7.9. Deploying FAS is easy, especially if you have full administrative rights to the private CA. Citrix recommends not using a server on top of another Citrix Components<\/strong>\u00a0are installed, or another server on the one that already Port 80 is used<\/strong> For example, IIS. Simply run the setup, which installs a Windows service and a console. Be sure to run the FAS console as an administrator (using runas); otherwise, further configuration will fail. Three tasks must be completed to finish the setup:<\/p>\n

    \n
  1. Upload (Import) Certificate Templates to the Private CA<\/li>\n
  2. Add the templates to the CA and<\/li>\n
  3. Authorization of the FAS server to issue certificates, which must be approved on the CA server.<\/li>\n<\/ol>\n

    1 and 2 are done via remote PowerShell and shouldn't be a problem.<\/p>\n

    \"Blog<\/p>\n

    If all tasks are \u201eGreen,\u201c a Microsoft Group Policy must be configured to define the FQDN and session settings of the FAS server. The policy must then be assigned to the VDA, DDC, and the FAS server itself. The configuration will not proceed until the policy has taken effect. If the system does not have the policy, the following will appear in the event log: No User Credential Service has been configured. Apply the \"Citrix User Credential Service Group\" Policy Object<\/code><\/p>\n

    \u00a0<\/p>\n

    User Rules \/ ACL<\/span><\/h3>\n

    The main task is to configure the Security Access Control List (ACL). By default, all computers are allowed access to StoreFront and VDAs prohibited<\/strong>. All computers involved must be added to the \u201eallowed\u201c list, and anything that is blocked must be removed. That's all there is to it.<\/p>\n

    \"Blog<\/p>\n

    \u00a0<\/p>\n

    FAS Configuration<\/span><\/h3>\n

    This is the tricky part, since not everything is currently documented, let alone for every possible scenario. The basic concept and architecture for some cases can be found in the Citrix eDocs (https:\/\/docs.citrix.com\/en-us\/xenapp-and-xendesktop\/7-14\/secure\/federated-authentication-service\/fas-architectures.html<\/a>), such as using ADFS for a B2B solution, etc., but no specific details on how to configure these, neither for Netscaler nor StoreFront. There is only one thing that is certain: Users must be familiar with the User Principal Name (UPN)<\/strong>\u00a0Please log in; otherwise, FAS will not be able to issue vSmartCards.<\/p>\n

    \u00a0<\/p>\n

    StoreFront FAS Plug-in<\/span><\/h3>\n

    Currently, FAS cannot be enabled in the StoreFront console and must be configured via PowerShell. I recommend creating a separate store named \u201eFAS\u201c for this purpose. The PoSh commands then use the path Citrix\/FASAuth. This modifies the web.conf file in the folder and is also replicated in a StoreFront cluster. Here are the PoSh commands for a store named \u201eFAS\u201c:<\/p>\n

    & \u201c$Env:PROGRAMFILES\\Citrix\\Receiver StoreFront\\Scripts\\ImportModules.ps1\u201d<\/code><\/p>\n

    $siteId = 1<\/code>
    $storeVirtualPath = \u201c\/Citrix\/FAS\u201d<\/code>
    $authenticationVirtualPath = \u201c\/Citrix\/FASAuth\u201d<\/code><\/p>\n

    # Use FAS<\/code>
    Set-DSClaimFactoryName \u2013siteId $siteId \u2013virtualPath $authenticationVirtualPath \u2013factoryName \u201cFASClaimsFactory\u201d<\/code>
    Set-DSVdaLogonDataProviderName \u2013SiteId $siteId \u2013VirtualPath $storeVirtualPath \u2013VdaLogonDataProviderName \u201cFASLogonDataProvider\u201d<\/code><\/p>\n

    \u00a0<\/p>\n

    FAS Use Cases<\/span><\/h3>\n

    There are many different scenarios possible, some of which can become quite complex, but ultimately, all of them involve accessing a full Citrix ICA\/HDX session. This brings me back to the beginning of the article, though not necessarily to the first use case.<\/p>\n

    What I see as the first use case for FAS is simply\u00a0Domain Pass-Through<\/strong> with StoreFront. If domain pass-through is enabled in StoreFront, it applies only to the Web Receiver (RfW) but not to the target VDA server. To make this work, the local receiver must be installed with administrator privileges so that SSO can be registered. Then SSO must still be configured via GPO, and in the end it doesn\u2019t work anyway because additional \u201ecredential providers\u201c that were loaded prevent the feature from functioning. All in all, it\u2019s not exactly simple or error-free.<\/p>\n

    With FAS, you can simply forget about the SSO part of the receiver! No admin installation, no receiver configuration for SSO!<\/strong> Don't forget: this requires a client in the domain, and RfW must be in the Intranet zone in Internet Explorer.<\/p>\n

    Back to the \u201eToken Only\u201c use case, a good example of FAS. Let\u2019s assume that all employees in the company use smart cards and do not know their Active Directory password. When employees work from home and do not use a company-issued device, How can they authenticate themselves without a password?<\/strong>? Token authentication using a UPN as the username is all that is required with FAS. This allows employees to work securely\u2014without a password\u2014both inside and outside the company.<\/p>\n

    \u00a0<\/p>\n

    FAS Improvements<\/span><\/h3>\n

    Citrix will and should continue to develop FAS, and by that I don\u2019t just mean FAS itself, but more importantly its integration with StoreFront and Netscaler. StoreFront needs better front-end error messages (simply saying \u201erequest cannot be completed\u201c isn\u2019t helpful), and FAS should be included as an authentication option in the console. Netscaler should include FAS options for SSO in the session profiles. FAS itself should get a \u201cfacelift\u201d for the console, along with better error messages, tracing, and logging functionality.<\/p>\n

    That said, FAS is very stable and easy to configure. Identity management is becoming increasingly important, and FAS serves as a bridge to enable users to access an HDX session.<\/p>\n

    \u00a0<\/p>\n

    My thanks go to Andrew Innes (FAS) and his team, as well as to Simon Frost (StoreFront)<\/strong>\u00a0\u00a0<\/p>\n