Facing an issue configuring a per-app vpn with pulse secure and airwatch. We set VPN to per app and correctly associated the vpn profile with our app, but it simply will not call the VPN profile, will not connect automatically, and if we do manually connect, the connectivty it not per app but whole device.
VMWare confirms the config is correct, and kind of point at pulse integration as the root cause. Pulse is confused they even are partnered with VMWare per our call with their engineers. Anyone have any experience deploying per app for android w/ airwatch and can share any wisdom or success/failure with this integration?
Per-App VPN with Airwatch Integration should work fine, and I've not deployed it using A.watch (deployed using Pulse Workspace).
What type of authentication being used for connecting to VPN? Cert or user/pass? Certificate authentication should be used for Per-App VPN (by design).
It is cert based auth. This works fine if we call the VPN manually. Are you aware of any current documentation that speaks to android and airwatch config w/ pulse? The only documentation I can find is several years and airwatch versions out of date
@sloving Is it possible to record the behavior and provide high-level logs from the pulse mobile client for review?
Replicate after enabling high-level logging on the client >> settings >> log settings >> clear >> log level >> high, then proceed to open vpn apps, wait for few seconds and then collect the logs (in event of pulse client not launching at the bg.)
@sloving Can we enable "Stealth-Mode" for AfW profiles on Airwatch?
I just replicated the setup with our Pulse Workspace not having "Stealth-mode" enabled but enabled "On-demand" connect type and perapp VPN did not kick-in...!
It works only when both set to true..
Stealth Mode: True
Vpn Certificate Auth: Yes
Vpn Connection Type: onDemand
Vpn Enabled: Yes.
Vpn Verify Certificate: Yes
Vpn Host: <Pulse Connect Secure sign-in URL>