Posts

Post not yet marked as solved
7 Replies
Hi Matt, So startVPNTunnelAndReturnError does not return an error - it completes successfully. Checking the NEVPNStatus AFTER completion of the call does show that the connection status is Disconnected. However, this by itself is not enough for me to deduce it is an authentication failure. I do see the "last disconnect error for <vpn name> changed from "none" to "The VPN credentials are invalid" in the Console app. I was hoping to get access to the "last disconnect error" programmatically. Also fyi, this app is targeted to MacOS and I am running it directly on my MacBook.
Post not yet marked as solved
7 Replies
Thank you for your response Matt. From the NEVPN documentation, my understanding is that the error you are catching in the code snippet can be one of : NEVPNErrorConfigurationDisabled NEVPNErrorConfigurationInvalid NEVPNErrorConnectionFailed NEVPNErrorConfigurationStale NEVPNErrorConfigurationReadWriteFailed NEVPNErrorConfigurationUnknown So, I won't be able to tell if there was an authentication failure, right? I am using EAPExtendedAuthentication and have saved a VPN profile with a persistence reference from the keychain. I believe my startVPNTunnelAndReturnWithErrors (I'm using ObjectiveC) succeeds without generating an error. I only get a system alert pop-up telling me that the authentication failed. I am not sure I understand why I would get an OSStatus error before calling startVpnTunnel since the authentication is done by the server?
Post not yet marked as solved
4 Replies
Hello, I am having the same issue with my installer and am using pkgbuild/productbuild as well. Was curious if there has been any update regarding this issue? Thx