Finding in the Wild | Citrix FAS – SSO No Longer Works After an Upgrade?

During Citrix upgrades, I check not only VDA registration and session launch but also the entire authentication chain. Citrix Federated Authentication Service (FAS) has an interesting change introduced in version 2511 that is easy to overlook in mixed

During Citrix upgrades, I check not only VDA registration and session launch but also the entire authentication chain.

Citrix Federated Authentication Service (FAS) has an interesting change introduced in version 2511 that is easy to overlook in mixed environments.

The symptoms:

❌ Users can sign in to StoreFront
❌ The published desktop starts, but Windows SSO fails
❌ Certificate templates and CA configuration look correct
❌ Not all VDAs behave the same way

🔍 What is behind this?

With FAS 2511, Citrix introduced the new V2 ticket format.

The key difference:

Previously (V1):
The VDA needs the FAS server addresses through the familiar registry/GPO configuration.

New (V2):
The FAS address is supplied directly in the ticket.

For VDAs running version 2511 or later, this eliminates the separate FAS address list.

⚠️ The crucial point:

In a mixed Citrix environment with older and newer VDAs, the existing FAS configuration must not simply be removed.

Older VDAs still need the FAS server addresses.

🛠️ My investigation process:

1. Compare FAS and VDA versions.
2. Check whether the FAS server addresses are still configured on older VDAs.
3. Examine Application Event 204 on the FAS server. It identifies whether V1 or V2 tickets are being used.
4. Only then investigate certificates, CA templates and permissions.

💡 My takeaway:

Not every FAS SSO issue originates at the certification authority.

FAS V2 simplifies the architecture, but only if every participating VDA supports the new ticket format.

For LTSR migrations and mixed VDA versions in particular, the FAS ticket version therefore belongs on my troubleshooting checklist.

SAML Authentication between Citrix & Microsoft with Azure MFA

Update to the latest cloud navigation.

As a result of increasing projects, here is a little how-to with the summary of my previous articles. The main points are:

  • Azure AD Seamless Single Sign-On (PTA / PHS)
  • SAML Authentication (Azure AD as IdP & Citrix Gateway as SP)
  • Citrix Federated Authentication Service (FAS)
  • Microsoft Azure Multi-Factor-Authentication with Conditional Access

Requirements

  • Fully working Citrix Virtual Apps and Desktop Environment (StoreFront & DDC Minimum Version 7.9)
  • NetScaler with successful base configuration & activated Enterprise or Platinum license (Minimum Version 12.1 Build 50+ for native workspace app, for browser Minimum Version 11.1)
  • Configured Unified Gateway vServer
  • Internal and external DNS entries for Unified Gateway vServer (e.g. citrix.deyda.net)
  • Certificates for DNS entries (wildcard certificates are the easiest)
  • Existing Azure Tenant with Azure-AD base configuration (Domain, AAD Sync) & activated Azure AD Premium license
  • AD Connect version installed and configured (Minimum Version 1.1.644.0)
  • Firewall release for *.msappproxy.net on port 443
  • Domain administrator credentials for the domains that connected to Azure AD via AD Connect
  • Installed Authenticator App on Test User Mobile Phone
Continue reading “SAML Authentication between Citrix & Microsoft with Azure MFA”

Citrix Virtual Apps and Desktops & WEM 2003 is released

The new current releases of Citrix Virtual Apps and Desktops, Workspace Environament Management & Citrix Provisioning are now available. They contains many new features compared to the last LTSR.

Citrix Virtual Apps and Desktops 2003
Continue reading “Citrix Virtual Apps and Desktops & WEM 2003 is released”