Hide Forgot
Description of problem: Both the CLI and network manager openconnect clients do not connect using the selected profile. What ever profile is alphabetically first is selected Version-Release number of selected component (if applicable): 5.01-1 How reproducible: Every time Steps to Reproduce: 1.Connect to Cisco Anyconnect VPN 2.Select profile from list 3.Enter username 4.Observe failure to connect 5.Check Cisco VPN logs to see that first alphabetical profile was actually requested Actual results: Connects using first profile Expected results: Connects using selected profile Additional info: I worked around this by making the profile I need alphabetically first by adding "aa" to the begining of the profile name. For example, my profiles are admin-ipsec and admin-ssl. Even when selecting admin-ssl, the VPN logs show that admin-ipsec was requested by the client. Changing admin-ssl to aadmin-ssl allows a connection, however no other profiles can be selected due to this bug. I've uninstalled and reinstalled both the openconnect and openconnect networkmanager packages before changing the alphabetical order
The same problem exist for openconnect-5.01-4 on Fedora 20. I've raised the priority to urgent, as there is no workaround for this bug unless you can arbitrarily change the profile names, which I cannot do.
openconnect-5.02-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/openconnect-5.02-1.fc19
openconnect-5.02-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/openconnect-5.02-1.fc20
openconnect-5.02-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
openconnect-5.02-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.