[Pidgin] #15669: XMPP: Unsaved but cached password should be cleared on invalid-authzid
Pidgin
trac at pidgin.im
Fri Jun 14 15:13:06 EDT 2013
#15669: XMPP: Unsaved but cached password should be cleared on invalid-authzid
----------------------------------------+---------------------
Reporter: xnyhps | Owner: deryni
Type: defect | Status: new
Milestone: | Component: XMPP
Version: 2.10.7 | Resolution:
Keywords: invalid-authzid jabber.org |
----------------------------------------+---------------------
Old description:
> When using an incorrect password on jabber.org, it returns {{{invalid-
> authzid}}} instead of what should be {{{not-authorized}}}.
>
> If Pidgin is set to not save a password, then the password is still
> cached in memory. Only on {{{not-authorized}}}, this cached password is
> automatically removed (causing a reprompt). On any other auth-related
> error the cached password is kept. The only way to remove this password
> is by entering a value in the account's preferences and clear it again.
>
> Because Pidgin doesn't support using an authcid different from an
> authzid, I think it's fair to tread {{{invalid-authzid}}} as a reason to
> clear the cached password.
New description:
When using an incorrect password on jabber.org, it returns {{{invalid-
authzid}}} instead of what should be {{{not-authorized}}}.
If Pidgin is set to not save a password, then the password is still cached
in memory. Only on {{{not-authorized}}}, this cached password is
automatically removed (causing a reprompt). On any other auth-related
error the cached password is kept. The only way to remove this password is
by entering a value in the account's preferences and clear it again.
Because Pidgin doesn't support using an authcid different from an authzid,
I think it's fair to treat {{{invalid-authzid}}} as a reason to clear the
cached password.
--
Comment (by Robby):
:P
--
Ticket URL: <https://developer.pidgin.im/ticket/15669#comment:2>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list