Bug 157843 - NM doesn't prompt you for a new password when saved vpn password changes
Summary: NM doesn't prompt you for a new password when saved vpn password changes
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Robert Love
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-14 03:32 UTC by Dan Winship
Modified: 2006-03-15 17:06 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Winship 2006-03-14 03:32:59 UTC
I was forced to change my password, and then the next time I tried to connect to
the vpn, it failed, with a "user or password incorrect" error. But it didn't let
me change the password. I had to go and delete it from gnome-keyring-manager.

This might be specific to NM-vpnc
Comment 1 Robert Love 2006-03-14 03:35:16 UTC
GNOME keyring?

You could do VPN -> Configure -> Edit and change the username and/or password, no?
Comment 2 Robert Love 2006-03-15 16:06:36 UTC
...

You can change the username and password in the VPN configuration tool.
Comment 3 Dan Winship 2006-03-15 16:14:37 UTC
oops, forgot to reply. This is with NetworkManager-vpnc. There is no
password field in its edit dialog.
Comment 4 Robert Love 2006-03-15 16:22:26 UTC
Oh, got it.  This needs to be fixed.
Comment 5 Robert Love 2006-03-15 16:38:12 UTC
Wait.  The next time you try to connect, it asks for the password.

Its hard to ask for the password in response to the failure because of the plugin nature of the VPN.  But the applet should recheck username/password on subsequent connections following an error.

Did you not see this, or is this not sufficient?
Comment 6 Dan Winship 2006-03-15 16:54:06 UTC
I assumed it would just fail again if I tried again, so I didn't try again until after I'd deleted the password from my keyring.

Does it actually understand what the error is or is it just echoing an error string from the server that it doesn't know how to interpret? If it knows what went wrong, it seems like it ought to let you correct it right then and there, rather than making you tell it to reconnect and then asking for the info. But if it doesn't actually understand the error, then I don't know if there's anything better it could do than what it does now.
Comment 7 Robert Love 2006-03-15 17:06:03 UTC
It just echoes an error string.  I suppose we could snag the string and parse it, but the code to handle this case is going to be quite large -- involving the VPN daemons, NM daemon, and the applet.

I just tested that it prompts for the username/password on reconnect when the login fails.

With the Code10 code freeze in place, WONTFIX.