Forum Discussion
The thing you're using is called "windows logon integration", or at least that's what F5 calls it. That 702 error can happen if the SSL handshake doesn't work for some reason. Make sure you haven't messed with the ciphers in the clientssl profile.
If that doesn't fix it, probably time to open a support ticket.
- Wompi_203183Aug 04, 2016Nimbostratus
Hi,
thank you very much for your answer. I haven't changed any cipher suites in the client ssl profiles.
Accidentially I have found a workaround. After your answer I have seen that the ltm showed the following message:
Connection error: ssl_shim_vfycerterr:4530: application verification failure (46) during vpn login.
With this message in google I stumbled across "On-Demand Cert Auth". Before we had only set require in client ssl profile. If we use "On-Demand Cert Auth" with require in APM and set the client ssl profile to ignore the VPN with smartcard auth works again with the dial up connection and windows logon integration.
Thank you very much.
Best regards
Mark
- Lucas_Thompson_Aug 04, 2016Historic F5 Account
Oh, that's very interesting. Glad you've got it working. What documentation have you been using to set it up? I'd like to double check that it has the correct information in this area.