#Citrix workspace app for windows upgrade
Users will be forced to upgrade their client to be allowed entry. Block: Post-EPA failure, the user will be prompted with a page indicating their Workspace App is out of compliance (would also display if they skipped the scan) and they have been denied access to the Citrix Gateway authentication page.This allows organizations to provide ample warning to end-users about the need to address the gap, to mitigate being caught off-guard in the future.
The user can click “Continue” to proceed to the login page. Warning: Post-EPA failure, the user will be prompted with a page indicating their Workspace App is out of compliance (would also display if they skipped the scan) and that they will need to upgrade to avoid being outright blocked from logging in, in the future.To address that concern, I am coupling the Endpoint Analysis (EPA) action with two login schemas: Do we just add some logon page footer text advising the user of what the supported client version is and where to get it and then block them when their client version does not match? This may work for some organizations but may be a little too ham-fisted for others where white gloving the user experience has to be balanced with operational and security mandates to minimize backlash from users. But what we do with that information, especially in the context of user experience is another. Scanning for a valid CWA version we’re willing to accept for external users logging in via Citrix Gateway to maintain standards and mitigate security risks of legacy clients is one thing. Special thanks to Allen Perry for his insights from the field on this one. With this in mind, I am proposing a registry scan target for the CWA version that leverages some standard REG_DWORD values Citrix has maintained for some time and presumably will keep using for a while yet. Note: Companion article for Workspace app for MacOS and Linux is now live.
#Citrix workspace app for windows how to
The means of how to scan for the Citrix Workspace App (CWA, formerly Citrix Receiver) for Windows has been a topic of debate for some time amongst the talented Citrix admins community. Something that I’m still personally surprised has not been baked into the Citrix ADC code more elegantly (be it for use on customer-managed ADCs or Adaptive Authentication which is more or less Citrix-hosted ADCs for customers to build complex auth flows on). The subject of this topic has been a long-standing request from customers and consulting engineers alike for years.
0 kommentar(er)
