You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
Sometimes the reconnect feature is not working using a smartcard.
Specifications
Version: 1.5.2
Platform: Windows 10 x64
Steps to Reproduce the Issue
Connect to a Cisco AnyConnect VPN by WIFI and using a Smartcard.
Config used: name, gateway, VPN protocol "Cisco AnyConnect", a system store id selected (from the Smartcard).
Disconnect.
(Optional) Close OpenConnect-GUI.
Switch to another different WIFI connection.
Open OpenConnect-GUI if closed.
Try to connect again to the same VPN (the Smartcard were not taken out in any moment).
In a random way you will be able or not to connect. If not running ok in the log view the line refusing the procedure is a line talking about a temp file generated.
Expected Behavior
Correct connecting to the VPN.
Actual Behavior
Sometimes is not connecting.
Workaround
In my case the workaround it is regenerate the temp file by opening my config file in the GUI and re-selecting in the list of system stores the id from the Smartcard (and storing the config file). It will generate a new correct temp file and it will pass for sure.
Source of the issue
For me the problem is in the GUI and its treatment of the temp file/certificate from the Smartcard. But I have not yet tested with the console, it would be the best verification. but no time yet to do it.
The text was updated successfully, but these errors were encountered:
Description of the Issue
Sometimes the reconnect feature is not working using a smartcard.
Specifications
Steps to Reproduce the Issue
Config used: name, gateway, VPN protocol "Cisco AnyConnect", a system store id selected (from the Smartcard).
Expected Behavior
Correct connecting to the VPN.
Actual Behavior
Sometimes is not connecting.
Workaround
In my case the workaround it is regenerate the temp file by opening my config file in the GUI and re-selecting in the list of system stores the id from the Smartcard (and storing the config file). It will generate a new correct temp file and it will pass for sure.
Source of the issue
For me the problem is in the GUI and its treatment of the temp file/certificate from the Smartcard. But I have not yet tested with the console, it would be the best verification. but no time yet to do it.
The text was updated successfully, but these errors were encountered: