In this article:

     

    Note: This bug was resolved in Jamf Pro version 11.12.1

     

    The latest version of Jamf Pro (11.11) has a bug which will prevent the Twingate VPN Custom Configuration Profile from installing an any macOS device.

     

    This is a known Jamf issue and will hopefully be fixed in a future release.

     

    Jamf have provided the following workaround until the issue is resolved:

     

    This behaviour has been documented as PI122416, currently the Product issue is open in a critical state.


    The workaround currently involves building the profile outside of Jamf Pro and signing it with a different signing certificate, to prevent Jamf Pro from making changes on upload. We suggest using a tool like iMazing Profile Editor to create your custom configuration profile for VPN, and when exporting the the profile, sign it and then upload the signed payload to Jamf Pro. Successful upload will show in Jamf Pro that the profile is signed and signature removal is required to make changes. Do not remove the signature, and deploy the profile as per normal.