https://bugs.meego.com/show_bug.cgi?id=19665 Summary: shared credentials Classification: MeeGo Projects Product: SyncEvolution Platform: --- Version: unspecified Platform: Common Architecture: --- Status: NEW Severity: normal Priority: Undecided Component: SyncEvolution AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: patrick.ohly(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-default-bugs(a)meego.bugs Estimated Hours: 0.0 We have "username", "password", "syncURL" properties. If "password" is "-", then reading credentials looks up the password based on the given username and the syncURL in the GNOME keyring (or soon, KWallet). The "server" and "user" keys are used as search filter, with "server" equal to the syncURL minus the method prefix (i.e., http:// and https:// stripped). Storing a "password" not equal to "-" will automatically set the password value in the keyring if its usage is enabled (on by default in the D-Bus server, off in the command line). Retrieving the config via D-Bus transparently retrieves the credentials and sends them to the D-Bus client. I'd like to extend this so that the username doesn't have to be know in advance, and so that CalDAV and SyncML can refer to the same server despite having different syncURLs. Here's how: "credentials = URI": Defines where credentials are stored. The empty string (default) is the traditional approach. "gnome://server=<server>[&user=<user>]" takes username and password from the corresponding entry. "kde://" does the same for KWallet. "keyring://" is an alias for the default keyring (depends on how the binary was compiled and runtime environment). Saving a config will always update the "credentials" property with the actual location. Here are some use cases for this: * The "google" and "google-calendar" configs will have "credentials = keyring://server=google" set. In the case of "google-calendar", both the sync and source configs have that. That way all three configs use the same username/password automatically. It forces command line users who do not want to or can't use a keyring to configure with empty "credentials"; they can't share credentials. * After configuring via the D-Bus interface, the command line will automatically enable the right access method for the credentials. It is no longer necessary to explicitly say "syncevolution --keyring". * A future extension would use either a different method or additional parameters in the URI to define some other authorization method. The current implementation must throw an error when running into something it doesn't know. Nothing needs to be done in the UI or the command line to support this. The only changes will be in the current code which talks to the keyring(s). -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: normal Priority: Undecided Keywords: Status: NEW Who: patrick.ohly(a)intel.com Assigned To: syncevolution-bugs(a)meego.bugs Target Build: --- Flags: Changed: -------- https://bugs.meego.com/show_bug.cgi?id=19665 -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug.