In trying to lock down access to a web application too only users within a XenApp environment. Is it possible to send the clientname in the HTTP payload by customizing something in the XenApp server (registry, etc)? These users will be using Internet Explorer in the xenapp session.
Similar in theory to how a proxy server passes a X-Forwarded-For header.
We know WHO the end-user, since the have authenticated, but we also need to identify the end-user device distinctly from other users.