--- Comment #5 from pohly <patrick.ohly(a)intel.com> 2011-09-14 10:18:32 UTC ---
(In reply to comment #4)
> This might be the root cause of the problem: is the GNOME
keyring unlocked in
> the environment in which the HTTP server runs?
How can I find this out?
You can start "seahorse", the GNOME keyring UI. If it shows your stored
credentials without asking for an unlock password first, then the keyring
I started the syncevo-http-server from the same
konsole as the syncevolution --configure
Then it should still be unlocked. Need to look for a different explanation...
Found it. When configuring the source with "--configure backend=...
database=... backendpassword=... @foo bar", an entry in the keyring tied to
"@foo" and "bar" is created (to be precise, the object key is
When retrieving the password as part of a HTTP server sync session for a client
"xyz" configured inside the @foo context, the object key is "xyz@foo bar
backend", which doesn't match the stored password.
We never found a good way to define lookup keys for source passwords. In
contrast to sync properties which are tied to a specific syncURL and thus peer,
for a source we only know how it is looked up in the SyncEvolution backend. We
don't even know at that level that the "database" is inside EDS.
Anyway, the solution is to use only the context as part of the object key, so
that "@foo bar backend" is used in all cases.
Alain, does that match your problem? Originally you gave a command line which
set the password in a normal config, but the real problem was in the HTTP
server setup, right?
... and syncevolution --export $HOME/calendar-backup.txt n900
calendar fails to
read the password from the keyring too (the evolutionpassword needed to connect
I can reproduce that. A partial fix for this was part of bug #21311, but now
that I look at the fix more closely I see that it didn't address passwords for
a source and also only worked for --print-items, but not for
I have a full fix for that.
MeeGo Release: unspecified
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
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.