Bug 1374876 - Does not connect or prompt for credentials
Summary: Does not connect or prompt for credentials
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-vpnc
Version: 23
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-09 23:10 UTC by ben
Modified: 2016-12-20 21:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 21:29:10 UTC
Type: Bug


Attachments (Terms of Use)

Description ben 2016-09-09 23:10:52 UTC
Description of problem:
After inputting the configuration for a VPNC-based VPN correctly, omitting the user's password but setting it to prompt each time, trying to connect does not bring up a password prompt, the VPN automatically disconnects instantly. 

Version-Release number of selected component (if applicable):
NetworkManager-1.0.12-2.fc23.x86_64
NetworkManager-vpnc-1.0.8-1.fc23.x86_64
NetworkManager-vpnc-gnome-1.0.8-1.fc23.x86_64


How reproducible:
Every time.

Steps to Reproduce:
1. Setup a vpnc VPN, in NetworkManager.
2. Input the Gateway, User name, set the password to "Ask for this password every time", input the Group Name and Group password.
3. Save.
4. Try to connect.

Actual results:
The VPN icon instantly disappears. If using the VPN properties window, the switch moves back to Off instantly. No popup appears to request the password.

In the journal, this line shows:
(date) (machine) NetworkManager[(pid)]: <error> [(date-in-seconds)] [vpn-manager/nm-vpn-connection.c:1918] plugin_need_secrets_cb(): (vpn uuid/name) final secrets request failed to provide sufficient secrets

Expected results:
VPN connects

Additional info:
Putting the exact same information into a vpnc .config file and connecting from the terminal requests the password and connects normally.

Comment 1 Thomas Haller 2016-09-11 19:37:51 UTC
you need a so called "secret agent". That is a program which asks the user for the password (or retrieves a password via other means, for example from the user's keyring).

Such an agent can be nm-applet, gnome-shell, plasma-nm, or nmcli (in newer versions).

Handling of passwords for VPN is special, which of the above agents will work depends on the version.

Certainly it should work if you install NetworkManager-vpnc-gnome package and have nm-applet running. Can you try that, or verify that nm-applet is actually running? Thanks.

Comment 2 ben 2016-09-13 04:34:06 UTC
My version is Fedora 23 x86_64, and I'm reasonably up-to-date (I last updated a few days ago). I do have the NetworkManager-vpnc-gnome package installed (As stated in the bug report). I did not have nm-applet installed. I have installed that and started it and now when I try to connect through NetworkManager, I get a popup that says: "The VPN connection (ID) failed because there were no valid secrets." If I try to connect again, I get multiples of that same message but it does not pop up asking for the required password.

Comment 3 Thomas Haller 2016-09-13 09:05:18 UTC
sounds like a bug.


Can you attach a logfile with level=TRACE? See https://cgit.freedesktop.org/NetworkManager/NetworkManager/plain/contrib/fedora/rpm/NetworkManager.conf?id=c90ec2d8c8a12b44c908bf7f80b23059c29f68fa

Comment 4 Fedora End Of Life 2016-11-25 09:34:31 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 5 ben 2016-12-08 19:57:44 UTC
I cannot reproduce the bug in Fedora 24 after upgrading my laptop. With Fedora 23 going EOL in a few weeks, I don't think this will be a problem anymore.

Comment 6 Fedora End Of Life 2016-12-20 21:29:10 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
bug.

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.