Ike V2 VPN with Certificate auth stopped work after upgrade error MSG "User Authentication Failed"

Hi, I have client to site IKEv2 IPsec VPN to cisco router with authentication via certificate. It was working before upgrade to Catalina. I'm 100% positive no changes made on the router. Now it says "User Authentication Failed". Debug on the router side looks good, router verified certificate, assign IP from the pool, creates virtual interface etc. Authentication Settings on Mac set to <none> Certificate. I tried to delete VPN account on MAC and re-create again- same thing.


I do not believe anything encryption related, just to be consistent

Router settings:

I have this for Ikev2

crypto ikev2 proposal macos

encryption aes-cbc-256

integrity sha256

group 14

crypto ikev2 proposal win7

encryption aes-cbc-256

integrity sha1

group 2


This for IPSec

crypto ipsec transform-set aes256-sha1 esp-aes 256 esp-sha256-hmac

crypto ipsec transform-set aes256-sha1-win7 esp-aes 256 esp-sha-hmac


Error message on Mac side "User Authentication Failed" Can you please tell me what is the right way to debug IPsec (Ikev2) on Mac? I tried to find any logs related to the subj without success. 


I tried this: delete Server CA, User cert and user private key from keychain, remove VPN connection, reboot, re-import back server CA, user cert, user private key, in keychain for all the above: Trust CA, allow everything for the cert and private key. Re-create VPN connection. Same error. I guess Apple broke something fundamentally related to security and certificate/private key handling here...


Thanks a lot for any ideas/ help!

MacBook Pro 15", macOS 10.13

Posted on Oct 18, 2019 12:59 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 30, 2019 1:56 PM

SOLVED:

https://forum.mikrotik.com/viewtopic.php?f=2&t=153155&p=755967#p755967

It turend out, that in iOS13 & macOS Catalina Apple has added SAN certificate field verification and it fails in the new version because my certificates does not have any Subject Alt.


I re-created both certificates for client & server with subject alternative names field (SAN) configured:

Solution: create certificates with SAN fields configured

Now it's working on iO13 and macOS catalina

Similar questions

24 replies
Question marked as Top-ranking reply

Oct 30, 2019 1:56 PM in response to dmitriy183

SOLVED:

https://forum.mikrotik.com/viewtopic.php?f=2&t=153155&p=755967#p755967

It turend out, that in iOS13 & macOS Catalina Apple has added SAN certificate field verification and it fails in the new version because my certificates does not have any Subject Alt.


I re-created both certificates for client & server with subject alternative names field (SAN) configured:

Solution: create certificates with SAN fields configured

Now it's working on iO13 and macOS catalina

Oct 31, 2019 2:59 PM in response to dmitriy183

Here is update from Cisco TAC (below) which says that it is not possible to use SAN on Cisco IOS CA:


After replicating this on our lab and doing a lot of research we have found you cannot add the subject alternative name to a certificate create from the IOS CA.

Basically the command “subject-alt-name” is only intended to be used when doing a self sign certificate. As mention on the PKI configuration guide “This option is used to create a self-signed trustpoint certificate for the router that contains the trustpoint name in the Subject Alternative Name (subjectAltName) field. This Subject Alternative Name can be used only when the enrollment selfsigned command is specified for self-signed enrollment in the trustpoint policy.”

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_conn_pki/configuration/15-s/sec-pki-15-s-book.pdf

The only options left will be to use OpenSSL to add the field to the request but after trying it on our lab we found the IOS ca will just ignore that even when is properly added to the certificate request.

Oct 21, 2019 2:12 AM in response to dmitriy183

Hey,


same issue here.


Official announcement (IKEv1): https://support.apple.com/en-us/HT210432


Starting with iOS 13, IPsec supports HMAC-SHA-256 with IKEv1 VPN.

"To make sure that your iOS 13 and macOS Catalina clients can connect to your IKEv1 or VPN server, configure the server to truncate the output of the SHA-256 hash to 128 bits. Truncating to a smaller number of bits might cause the server to drop data that VPN clients transmit."


https://forum.mikrotik.com/viewtopic.php?f=2&t=153155&p=755967#p755967


Regards.



Oct 21, 2019 7:02 AM in response to dmitriy183

Unfortunately I dont have a MAC only iPhone and iPad. Mikrotik debug logs with SHA1 show that iPhone agrees with the use of SHA1. The funny thing is that if you see Mikrotik Active Peers you can see the connection is established and the tunnel working correctly. However iPhone thinks that an authentication error occurred. Thats why you see everything to be normal on Mikrotik side

Oct 31, 2019 7:55 PM in response to florianotpg

Yes TAC it is Cisco official support -we have network built on cisco devices and buy service contracts for them which gives us the right to bug their specialists. Yes openssl is another option. Does not really fit in my original setup to have all on one router. The funny thing is I have virtual box on mac and windows10 running on it. Native windows10 vpn client stopped work as well with certificate authentication. Im not sure if it related somehow to upgrade to catalina or not but it was working about month ago...

Oct 21, 2019 6:56 AM in response to fotisail

I will need to check what will be proposal from catalina on the router. I would expect that if proposal changed then router will reply with “no proposal chosen” which is not the case. As I said on the router side I do not see anything suspicious or I miss it. is there any way to turn on vpn debug on catalina side? Debug on the router side is quite noisy because it is production vpn concentrator.

Oct 21, 2019 12:58 PM in response to fotisail

Not a solution just reading - Cisco AnyConnect broken because of luck of 32 bit support and other requirenments, cisco released 4.8 version as fix.

https://www.cisco.com/c/en/us/td/docs/security/vpn_client/anyconnect/anyconnect48/release/notes/b_Release_Notes_AnyConnect_4_8.html?dtid=osscdc000283


This is what they said: Beginning with macOS Catalina release (10.15), the operating system will no longer support the executing of 32-bit binaries. Additionally, applications must be cryptographically notarized in order to be installed by the operating system. Cisco AnyConnect 4.8.00175 is the first version that officially supports operation on macOS Catalina and contains no 32-bit code.


Checkpoint VPN client broken as well, client will be available in December https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk163094


This is serious business impact as I see...

Nov 1, 2019 9:19 AM in response to florianotpg

I really do not like this voodoo. I switched my operations to client-vpn-less methods. Can not risk to loose access to the remote equipment every time MS or Apple "improve" their systems. Normally they have to provide "White Paper" with the technical details what they are going to do, but what I see is really non professional approach. Ok I'm done with it. Thanks a lot for your help and ideas!

Nov 1, 2019 10:18 AM in response to florianotpg

What I use- I have cisco routers everywhere (and in Azure too- they have CSR1000v- virtual router) and I built site2site VPNs between all these sites. I have 2 hosts on each site to which I can RDP or SSH and from that hosts I can get to the local and other sites, interconnected via site2site IPSec tunnels. This setup makes client2site vpn obsolete. These hosts used for "Supporting personnel" - regular users do not have VPN. File sharing done via "Cloud Drives". I'm network guy- do not know too much about MS apps- sorry- can not comment on that :-) We have Windows guys- they handled all these animals. I use cisco network equipment- Routers/switches/ASA-type firewalls are really stable with outstanding technical support from the company- use them from the time "before Internet" if I remember correctly- getting too old :-). Rest of the cisco products are just "Ok". I used clien2site to get to the remote equipment consoles/management- now I do it via "jump-hosts" :-)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Ike V2 VPN with Certificate auth stopped work after upgrade error MSG "User Authentication Failed"

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.