cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
995
Views
5
Helpful
0
Replies

CSCvw38645 - Ability to differentiate between ARM64 and normal ones when deploying AC automatically (web-launch)

Jerome BERTHIER
Level 1
Level 1

Hi

 

I think that there is already a way to differentiate platform when deploying AC from WebLaunch on the ASA (assuming that the client has not already any AC version installed).

You can bind a regex value condition with each AC package activated on the ASA.

This regex is parsed agains the user-agent value of the navigator. It is not totally reliable but it usually works correctly (and for years on my corporate user devices).

I already use this setup :

anyconnect image disk0:/ssl/anyconnect-linux64-4.9.03047-webdeploy-k9.pkg 1 regex "Linux x86_64"
anyconnect image disk0:/ssl/anyconnect-macos-4.9.03047-webdeploy-k9.pkg 2 regex "Intel Mac OS X"
anyconnect image disk0:/ssl/anyconnect-win-4.9.01095-webdeploy-k9.pkg 3 regex "Windows NT"

If there is no match with regex , the last package is proposed to the user.

 

I do not own any ARM64 device but it seems that the user-agent should contain ARM64 in the user-agent string (at least ARM I guess).

For example, like this for Firefox :

Mozilla/5.0 (Windows NT 10.0; ARM64; RM-1096) AppleWebKit/537.36 (KHTML like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393

 

So if you use this setup, it should be able to differenciate Windows x86_64 from Windows ARM64 :

anyconnect image disk0:/anyconnect-win-arm64-4.9.03049-webdeploy-k9.pkg 1 regex "Windows NT*(ARM64)+"
anyconnect image disk0:/anyconnect-win-4.9.03049-webdeploy-k9.pkg 2 regex "Windows NT"

 

Hope this helps.

 

Regards

 

Jérôme

0 Replies 0
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: