Per-App VPN Payload on iPhone using Configurator Profile

UnePierre
UnePierre Posts: 1 New Member

Hi,
Am I not in the right place for help with this?

I would like to set up VPN within F-Secure Total Security on an iPhone SE (2000) and on an iPad 9th generation.

They are supervised devices using Apple Configurator. Thus, I need to specify a so called payload in the config file.

In the attached PDF, there is the excerpt from the config file syntax manual detailing the available specs.

I would be very grateful - while also hoping that others in the community will profit - if you could provide me with the right choice of payload elements including the values to which I am to set them to configure F-Secure's VPN.

And also: In the documentation there is a section App-to-Per-App VPN Mapping. I would like to set up the device so that F-Secure's VPN only kicks in, when certain apps are launched or non secured WIFI connections entered by the user.

Thank you a lot!

Humbly yours.

UnePierre

Accepted Answer

  • Chameni
    Chameni Posts: 260 Moderator
    Answer ✓

    Hi @UnePierre,

    At the moment, F-Secure Total VPN on iOS/iPadOS does not support manual VPN configuration using Apple Configurator or custom MDM VPN payloads (such as IKEv2, IPSec, or custom Network Extension payloads).

    F-Secure’s VPN on iOS works as an app-managed VPN:

    • The VPN profile is created dynamically by the F-Secure app itself
    • Configuration, server selection, and tunnel control are handled internally
    • There is no exposed VPN payload schema (PLIST/XML) that can be defined or enforced externally

    Because of this, it isn’t possible to specify payload keys or values in a configuration profile to pre-configure or control the VPN behavior.

    Thank you for taking the time to share such a thoughtful and well-documented question, it will definitely be useful for others in the community as well. If you have follow-up questions or want to discuss supported deployment options further, feel free to let us know on this.

    Thank you.

This discussion has been closed.