Jump to content


Photo

Unsupported-client-type when enabling Federated Authentication Service

Started by Greg Arkin , 12 April 2017 - 07:42 PM
FAS
4 replies to this topic

Best Answer Greg Arkin , 20 April 2017 - 02:15 PM

Issue resolved, I didn't realize that the Citrix Agent version on the VDA machine I was connecting to was only 7.8, upgraded the agent to 7.13 and issue has been resolved.

Greg Arkin Members

Greg Arkin
  • 4 posts

Posted 12 April 2017 - 07:42 PM

I am attempting to setup Federated Authentication Service so I can use SAML Authentication with my Netscaler Gateway, but I am getting an error when I try to launch my desktop that states "Failed to launch the resource 'Controller.My Desktop $P1234' using the Citrix XML Service at address 'https://ddc.mycorp.local:443/scripts/wpnbr.dll'. The XML service returned error: 'unsupported-client-type'.

 

I used the Citrix setup documentation https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-13/secure/federated-authentication-service.html to configure my environment.  I am not sure what I am missing.

 

I am able to get authenticated to Storefront and enumerate my desktops, but when I click on the desktop to connect I get the error: Cannot start desktop "My Desktop" and then the error above gets logged in the Citrix Delivery Services log on my Storefront server.

 

We are running Storefront 3.8 and XenDesktop 7.13



Carl Stalhood CTP Member

Carl Stalhood
  • 11,954 posts

Posted 13 April 2017 - 12:53 PM

The Federated Authentication Service address GPO app applies to the VDAs too?

 

You can also verify with my documentation - http://www.carlstalhood.com/citrix-federated-authentication-service-saml/



Greg Arkin Members

Greg Arkin
  • 4 posts

Posted 13 April 2017 - 02:11 PM

Carl,

 

Yes the Federated Authentication Service address GPO applies to all VDAs, as well as all my Citrix Servicers (StoreFront and XenDesktop), I have validated the setting in the registry.

 

I reviewed you documentation and didn't see anything that I might've missed.

 

Thanks,

Greg



Greg Arkin Members

Greg Arkin
  • 4 posts

Posted 13 April 2017 - 02:53 PM

Some additional information from the XenDesktop logs -

 

The Citrix Broker Service logs Event 1106 stating "The Citrix Broker Service failed to broker a connection for user 'domain\user' to resource 'My Desktop'. The required protocol 'HDX' is not configured for this resource or the resource might not advertise this protocol.

 

I am not sure where I can configure the protocol.

 

Thanks,

Greg



Greg Arkin Members

Greg Arkin
  • 4 posts

Posted 20 April 2017 - 02:15 PM

Issue resolved, I didn't realize that the Citrix Agent version on the VDA machine I was connecting to was only 7.8, upgraded the agent to 7.13 and issue has been resolved.


Best Answer