Comment 21 for bug 532055
Revision history for this message
| Leonard Richardson (leonardr) wrote Re: Trusted credential-management apps are broken and doomed | #21 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
jml, we are talking about #1. Something like the desktop authorization clients packaged in Leonov, Ground Crontol, and ubuntu-dev-utils, but which actually works now and which will continue to work when Launchpad is an OpenID relying party.
I'm willing to consider _any_ client- and server-side design that will not require end-users to get Launchpad-specific credentials in addition to their OpenID provider credentials. I am as certain as I can be that this means opening their web browser at least once.
If we write a client-side tool that uploads your public SSH key to Launchpad, how does Launchpad know which Launchpad account owns that key? The user would have to be logged in to Launchpad through some other mechanism. This requires opening their web browser and sending them through the normal Launchpad login process where they log in to their OpenID provider.