On Thu, 2014-04-17 at 13:24 -0700, Todd Wilson wrote: > On Thu, Apr 17, 2014 at 5:26 AM, Patrick Ohly <[email protected]> wrote: > > Here's what it has stored for me for Google CalDAV: > > > > server: www.google.com/calendar/dav/%u/user/?SyncEvolution=Google > > user: [email protected] > > > > The "server" and "user" values are used to find the stored "password" > > value. I've not found good instructions for choosing keys. Make them too > > specific and you end up with more entries than necessary and the user > > has to fix them multiple times when changing the password on the server. > > Make them too unspecific and different passwords will conflict with each > > other. For example, an HTTP server might require different passwords for > > different paths, which is why SyncEvolution includes the path in the > > key. > > I don't see anything like this. I only have the "GOA google > credentials for identity account_nnn" entries mentioned above, nothing > to do with CalDAV. Where are you seeing this?
I looked at one of the network passwords created by SyncEvolution. In your keyring, that would be "[email protected]/dav/twilson" and "[email protected]/dav/twilson/Calendar". I have that for Google Calendar because I was accessing it via traditional Basic Authentication, not via OAuth2. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
