On Thu, Apr 17, 2014 at 5:26 AM, Patrick Ohly <[email protected]> wrote:
> > 1. As a precaution, I started up GOA, deleted my Google Account, and
> > re-added it, authenticating successfully inside the GOA application.
>
> Which version of GOA, which distro, and what permissions where you asked
> to grant?
>
> It is important that "Google Calendar" and (for Google Contacts) "Google
> Contacts via CardDAV" appear there. Yes, Google distinguishes between
> Google Contacts via their own API and CardDAV.
OK, one problem was that, even though I had GOA installed on my Ubuntu
system, the "Online Accounts" icon in the Control Center was taking me
to "Ubuntu Online Accounts", with no indication that this was the case
-- everything was just "Online Accounts". When I used this, as before,
to create a Google account and authenticate with Google, the
permissions dialog was:
Ubuntu would like to:
- Have offline access
and that was it. Some web searching turned up an alternative way of
starting the Control Center:
XDG_CURRENT_DESKTOP=GNOME gnome-control-center
which presents two "Online Accounts" icons. When I opened the other
one, created a Google account, and authenticated, the permissions
dialog was
GNOME would like to
- View and manage your mail
- Know who you are on Google
- View your email address
- Manage your calendars
- View and manage your spreadsheets in Google Drive
- View and manage any of your documents and files in Google Drive
- Manage your contacts
- View and send chat messages
- View and manage your contacts using the CardDAV protocol
Wow! Anyway, the two permissions you mentioned (calendar, contacts
using CardDAV) were there. After allowing access, I turned off the
toggles for Mail, Chat, and Documents, leaving only Calendar and
Contacts.
Back in seahorse, I see "GOA google credentials for identity
account_nnn" twice, now, with two different values of nnn. Looking at
the properties of these keys produces the same top-level result:
Use: Saved password or login
Type: Password
but I notice that the UOA password has password keys
access_token, access_token_secret
as reported before, whereas the GOA password has password keys
authorization_code, access_token, access_token_expires_at, refresh_token.
> > 3. I checked with seahorse and found an entry "GOA google credentials
> > for identity account_1322264161" (Gnome Online Accounts password). I
> > also found "Network passwords" for "[email protected]/dav/twilson"
> > and "[email protected]/dav/twilson/Calendar". Are those the entries
> > created by syncevolution in my Zimbra sync? Do I need both?
>
> Probably yes. If you look at the details of these network passwords,
> you'll see that SyncEvolution includes the full path as "server" key, so
> the two entries really are different. Whether they are still in use is a
> different question.
OK, I see what you're referring to here in these keyring entries.
> 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?
> > 4. Using the account information I got from Step 3, I entered the
> > command
> > $ SYNCEVOLUTION_DEBUG=1 syncevolution --daemon=no --print-databases
> > backend=caldav username=account_xxxxxxx
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> You need to tell SyncEvolution that you want to use GOA. This has to be
> username=goa:account_xxxxxx.
Now trying this again with the goa: username and my GOA account_nnn, I
see, at the end,
caldav:
Personal
(https://apidata.googleusercontent.com:443/caldav/v2/xxxx%40gmail.com/events/)
<default>
However, when I go to Google Calendar, create the new calendar that I
want to use to sync with Zimbra, and then repeat the
--print-databases, it again only finds Personal. Does this mean that
Google is only allowing CalDAV on your Personal calendar, or is there
something else I have to do to find this other calendar?
--Todd
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
