Do you have problem deploying all profile(s) other than the one with authentication payload? Have you tried having the F5 Per-App VPN payload included in a dedicated profile for deployment and check the result?
What are the active MDM API's reported by the device agent or in the web-console?
According to your post, you should be using OEM specific Android Plus device agent. If I remember correctly, Per-App VPN profile payload is only supported for a very small set of Android Plus device agents, and likely not for the Honeywell device agent. You might have to confirm this with Soti support team directly to confirm.
Hi Raimond, thanks for your reply.
We don't have any problem with other profiles deployment, just this one - that already is a dedicated one and fails.
Send an email to directly to support@soti.net
If you are lucky, Soti moderator or other experts from Soti on this topic might also directly give an answer in this forum if they see this thread.
Hi Enrico,
Thank you for requesting an answer on this post.
To progress your issue, it would probably be most efficient to open this as a case with SOTI Support (support@soti.net) since ideally we will need to investigate device logs to see what is happening when the Profile is being pushed.
In terms of compatibility, for your scenario the basic prerequisites would be to have an OEM-signed agent and ensure that any necessary third-party apps are already installed on the device when the Profile is pushed otherwise it will fail, but it seems you already have the browser installed. I will carry out further research and update this thread with some more information to verify the this.
Kind regards,
Thank you JSMOD for your reply.
I've opened a case with the support team.
Bye
Hi Enrico,
Just to follow up my previous comment, I have checked this and my understanding is that OEMs need to be whitelisted by the VPN provider to work. So from the information you have provided there is a chance that F5 has not whitelisted Honeywell devices.
However, more testing should be carried out with the Profile configuration and an investigation into the device logs, so for this reason it is very good that you have already opened a Support ticket with us.
Many thanks,