Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1657427 - plasma openconnect gui not showing and/or sending second password field when connecting to vpn
Summary: plasma openconnect gui not showing and/or sending second password field when ...
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-nm
Version: 29
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-12-08 03:31 UTC by Robert G. Werner
Modified: 2019-11-27 20:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-27 20:17:02 UTC
Type: ---

Attachments (Terms of Use)

Description Robert G. Werner 2018-12-08 03:31:47 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0
Build Identifier: 

After update reboot,  when I try to use the openconnect vpn GUI in KDE plasma to connect to my work vpn,  I only see the username/password field.  When I try and connect the login is denied because the vpn is expecting a second password field for DUO MFA authentication.

When I create the VPN for the first time,  the second password field is available,  and the connection works as expected.  But after I disconnect,  when I try to reconnect the second password field is missing and the connection fails with invalid credentials.

Reproducible: Always

Steps to Reproduce:
1.Create an openconnect vpn connection in the VPN section of your network connections applet.
2. In the networks applet,  click on the VPN you just created and click connect.
3. Check Automatically start connection next time and store passwords.
4. Click the connect button.
5. When prompted,  enter username, password and second password (in this case, "push" to get an DUO prompt).
6. Login and authorize yourself through duo.
7. Disocnnect
8. Click connect on the VPN again.
9. When it comes up,  the second password field is missing.
10. Connect and get denied "Credentials invalid".

Actual Results:  
Connection denied because the second password wasn't submitted.

Expected Results:  
Valid VPN connection established.

A work around is to change the VPN group to some other setting and then back to the group I use to authenitcate.  This seems to cause the client resubmit the request for the auth page.

Comment 1 Ben Cotton 2019-10-31 20:21:02 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2019-11-27 20:17:02 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.