FortiClient VPN for iPadOS fails with AES256-GCM and PRF-SHA384/SHA512 in IKEv2 Phase 1
FortiClient VPN 7.4.11.0198 on iPadOS 26.7.1 fails to establish an IKEv2 IPsec tunnel to FortiGate running FortiOS 7.4.12 build 2902 when Phase 1 uses AES256-GCM with PRF-SHA384 or PRF-SHA512.
FortiGate accepts the Phase 1 proposal:
ENCR: AES_GCM_16, 256 bit
INTEGR: NONE
PRF: PRF_HMAC_SHA2_384 or PRF_HMAC_SHA2_512
DH: MODP2048 or MODP3072
However, FortiClient does not send the subsequent IKE_AUTH request. FortiGate eventually reports:
negotiation timeout, deleting
connection expiring due to phase1 down
These combinations were tested:
AES256-GCM / PRF-SHA256 / DH15: works
AES256-GCM / PRF-SHA384 / DH14 or DH15: fails after IKE_SA_INIT
AES256-GCM / PRF-SHA512 / DH14 or DH15: fails after IKE_SA_INIT
AES256-CBC / SHA384 / DH15: works
Phase 2 with AES256-GCM works correctly when Phase 1 uses either AES256-GCM/PRF-SHA256 or AES256-CBC/SHA384. The problem occurs with both SAML SSO and local username/password authentication, although authentication is never reached in the failing cases.
I reproduced the issue on both an iPad and an iPhone running iPadOS/iOS 26.7.1. Has anyone else confirmed this behavior with FortiClient VPN 7.4.11, and is there a known solution, workaround, or bug ID?
Thanks in advance.
Best regards,
 Stepan Cirkl
