Start a Conversation

Unsolved

This post is more than 5 years old

C

33383

May 11th, 2015 06:00

Wyse Xenith and Citrix Access Gateway

Wyse Xenith and Citrix Access Gateway

Just a heads up to everyone. I have also cross posted this over on Citrix.


Wyse Xenith (As well as many/all other current Zero Clients as of 03-23-2012) does not support CAG 5.X.X. Not in any way, shape, or form.

The change to logon points in 5.X.X (as great as it is) broke the entire authentication chain as used in CSG/CAG4.X.

As of today, the only working options are as follows:

1. CSG - Works
2. CAG 4.X Std/Adv - Works in CSG Mode (No Auth in the CAG, purely a reverse proxy pass-through to the WI/hosts)
3. CAG Ent + Netscaler Lineup - I haven't tested it personally, but I am assured it works in CSG mode as above, plus RSA/LDAP Auth Modes.

Wyse supposedly has a roadmap entry to fix this, but it entails a significant rewrite of the auth/login routines. Apparently it will happen eventually, but no pubic ETA.

Citrix doesn't know anything about the incompatibility, and Wyse only knows about it up at L2/3.

There is a Wyse service document (open a case, level it to 2/3) which details getting the Xenith to work on Ent/Netscaler with RSA/LDAP. Getting it to work in CSG mode is as simple as setting up CAGS standard and turning all the auth off (both in the groups and at the global).

Hopefully this post will help someone out there.

Karl P

May 11th, 2015 06:00

Smile We support now

We have a build now which supports CAG VPX in CSG mode. This fix will now b part of next released build.

21 Posts

May 11th, 2015 06:00

Quote Originally Posted by Anirban Mukherjee View Post

We have a build now which supports CAG VPX in CSG mode. This fix will now b part of next released build.

 

Using CSG mode completely defeats the purpose of using Access gateway. This is useless until it will support authentication at the access gateway.

6 Posts

May 11th, 2015 06:00

I think I am running across this issue? I had a Xenith 2 working fine by pointing it directly to my vdimanager with Vdi-in-a-box for logging in. I just setup the CAG version 5 and when I changed the address to the CAG I could not login with the format https://(CAG ADDR)/lp/pnagent which works for other devices like the iPad. I would get the message that it could not log in. If I changed the url format to https://(CAG ADDR)/http/(IP ADDR VDIMGR)/dt/PNAgent/config.xml I was able to login at the login prompt and see my VM's but it would not connect me. Instead I got a message to the effect that the VM refused my connection.

Is this what you all are seeing? Any word on a fix? For now I am fine because I dont see the need to deploy a zero client outside our firewall.

No Events found!

Top