Comment 55 for bug 595551
Revision history for this message
|
|
#55 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I don't have technical backend to help on this; but I can still help other users.
> we need a way to directly specify user and password for a given request.
I think there is no clean way to do this. Because ... if we do path-level specific stuff, we will have to do server/domain specific patches in the end. Google has it's own way to interpreet the RFC. Other services will do it a different way.
So, hardcoding an exception for Google is not acceptable.
Doing a per server configuration seem to be a mid-stage solution. But, as the GUI front-head is per-user-account oriented, having a per server thing in the backend is really not a good idea. A per-server configuration chould be done in the preference settings. To allow one server to assume foobar.com/a/b to be different from foobar.com/a/c, and still allow foobar.net/a differ from foobar.net/d . A two columns configuration pannel, like for password: left=server, right = path length to be "user specific", don't ask password under below this lenght, ask different username if higher.
This could work, but, i think it's not clean enough, and that the dev team will reject my idea.
IMHO, the root problem is that the password manager, and the account manager are orthogonal. In THIS case, we almost need a per account password, what is impossible due to the design of the Mozilla suite. We need to cut the orthogonality.
Why does this problem NOT happen with Imap ? If calendars are specific use case, and cal passwords are managed a different way than Imap, then, my idea is not so stupid: we could write "password retention rules" ... that would be cal specific ... and, cal specific options in the Preference menu. Thus, my idea to add a new Cal entry in the pref menu. To allow, and custom Cal specific password retention policies.
In fact, the root problem of the bug is that, servers don't segment "user profile" at the same depth. So, we need to let the "user" custom this in a way or an other. Can not be per account; so, NOT in the account manager.
My 2c.