Jump to content
Welcome to our new Citrix community!
  • 0

FAS to XenDesktop Pub Desktop to Pub Application SSO pass through


David Ray

Question

We are using SAML with an external identity provider through Netscaler and Storefront using FAS to our published desktops in Xendesktop.   This is working pretty well.

 

Within the published desktop (pooled, random, provisioned by PVS) we have Receiver installed with SSO/Pass-through for access to a few published applications that are not in our image for one reason or another.


 


 

The scenario works fine when you login the normal way... userid and password at Storefront or Netscaler.  

 

But when going in via SAML the Storefront logs into the pub desktop VDA with a SmartCard Cert provided by FAS.  This works fine... except for Receiver and the published apps.  Receiver obviously has nothing to pass on to the XenApp VDA to logon.  When you try you get a server 2008 console screen in a window.  You can click Switch User and logon... although the application does not actually start.  I have configured Storefront to allow SmartCard authentication but that does not fix it.

 

I have tried latest versions of Storefront (3.9) and Receiver (4.8).  VDAs are 7.13.

 

Anyone know if it is possible for this to work and if so how?

 

I made a nice(ish) ascii diagram I was going to paste here but you cannot choose a monospaced font so it looks bad.  Here is a link to the ascii diagram if you are interested.  Also attached it in a text file if you are leary about clicking on links (reasonable).

 

Thanks,
David

 

 

 

FAS_SSO_Problem.txt

Link to comment

21 answers to this question

Recommended Posts

  • 0

Well... I really hate to go on record for the whole internet to see... but it is working now.  And I am not sure when it started working.

 

René, yeah, all those things you mentioned last I had already checked.  I really think my problem was probably in getting my VDI environment switched successfully from the old Storefront stores with old 6.5 XenApp to the new Storefront stores with new FAS configured 7.x XenApps.  Some configs were baked into the image, some were GPO.  Hard to get them all right at the same time.  I probably got it fixed at some point and didn't realize it.

 

Still, it's odd... I had it fixed enough to get the screenshot I attached earlier.  I don't know... it's working now.

 

Anyway, thanks René, the fact that you understood what I was doing and could say it worked for you gave me confidence to keep plugging away at it.

 

See ya,

David

  • Like 1
Link to comment
  • 0

Sorry to be so slow to respond... I went on vacation and tuned all this out for a while.  I did try that (enabling InSession Certs).  It does not help.  And that stands to reason I think.  Receiver pass through auth probably doesn't know anything about Smart Card certificate authentication.

 

/David

Link to comment
  • 0

Apparently I am not doing a good job of explaining.  There are no visible errors.  The applications work fine if you run them directly from Storefront.  What I am doing is publishing the applications to a XenDesktop desktop.

 

My users use XenDesktop desktops for nearly all their work.  A few users get special applications published to their Xendesktop desktop from XenApp.  This works fine using the normal logon methods (Userid/Password to Storefront/Netscaler Gateway).

 

The breakdown is when when the users login using federated authentication.  In our case we are using a service with Netscaler to provide Multi-factor authentication.  The Netscaler using SAML and the Citrix Federated Authentication Service (FAS) to authenticate to the Xendesktop desktop.  So far so good... this works.

 

But then when the user attempts to access the published app (or sooner if I have pre-launch enabled) they just get the Windows Server 2008 R2 (our XenApp server OS) logon dialog because Receiver has (apparently) failed to pass-through the authentication. (Screenshot attached.)

 

Maybe I am the only person to ever try this.  My coworker spent hours with Citrix Support and got basically no where (although he may have been worse at explaining than I have been).

 

It is unclear to me if this can never work and I am wasting my time or if it just something with my environment that if I could fix would then work.  

post-12492685-0-27375000-1504103707_thumb.png

Link to comment
  • 0

hmm that's strange. once again i would doublecheck the FAS gpo on your XenApp. look in registry if the fqdn is really applied. check. some other things to check:

- single domain?

- check user rules on FAS (all storefronts and VDAs allowed)?

- stores on the storefronts in question are enabled to request claim by running the ps script?

Link to comment
  • 0

If you are using FAS for the first hop (i.e. to reach the published desktop), you cannot use Receiver's SSO feature (since this uses a credential capture mechanism that won't work with FAS).

 

Here's how the deployment should be configured:

 

- Receiver SSO NOT enabled as noted above

- Second hop StoreFront configured for "domain pass thru" (will allow Receiver to SSO to second hop StoreFront to enumerate published apps)

- Second hop StoreFront FAS enabled (will allow SSO to second hop VDA where app is hosted)
 

The FAS server(s) used by the second hop StoreFront can be the same OR different from the FAS server(s) used by the first hop StoreFront - it doesn't matter.

Link to comment
  • 0
2 hours ago, David Williams1709151547 said:

If you are using FAS for the first hop (i.e. to reach the published desktop), you cannot use Receiver's SSO feature (since this uses a credential capture mechanism that won't work with FAS).

 

Here's how the deployment should be configured:

 

- Receiver SSO NOT enabled as noted above

- Second hop StoreFront configured for "domain pass thru" (will allow Receiver to SSO to second hop StoreFront to enumerate published apps)

- Second hop StoreFront FAS enabled (will allow SSO to second hop VDA where app is hosted)
 

The FAS server(s) used by the second hop StoreFront can be the same OR different from the FAS server(s) used by the first hop StoreFront - it doesn't matter.

Thanks for the response David

- Receiver SSO NOT enabled as noted above

     Should we disabled SSOEnabled on Receiver?

And do we need to set AuthenticationService to FASClaimsFactory?

If 1st hop published desktop is accessed directly from Storefront when accessed internal network without FAS, still 2nd hop connection works?

Link to comment
  • 0

I tried to get around same problem by enabling smartcard pass-through in the default.ica file on the storefront, as figured the user has logged on with a smartcard class certificate issued by FAS.  Unfortunately, i couldn't get this to work, so looks like may need to resort to enabling FAS on second store.

 

https://docs.citrix.com/en-us/storefront/1912-ltsr/configure-authentication-and-delegation/configure-smart-card.html

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...