search

michael-adler / sync-google-contacts

Automatically exported from code.google.com/p/sync-google-contacts
18 stars 12 forks source link

ClientLogin is disabled, need to upgrade to OAuth 2.0 #10

Closed dschwen closed 4 years ago

dschwen commented 9 years ago

Google deprecated and disabled the password based authentication. This script need to be updated to utilize OAuth 2.0.

dschwen commented 9 years ago

0fcca64 makes a browser pop up to authenticate the app (needs a client secret generated at https://console.developers.google.com/project with type installed application). However when utilizing the API it complains about the user not being authenticated. I'll investigate further.

dschwen commented 9 years ago

I saw @dkelley044 had already implemented a working version of this. I changed the directories and the README a bit.

dkelley044 commented 9 years ago

I'd love for someone to pretty up my work and help me solve a couple problems I'm having. do you have the skills to help?

  1. I need to modify the feed I'm returning to google as far as XML namespace schemas for contacts. google contacts that link to a google+ profile and/or contacts that are modified in some contexts contain xml extended attribute tags with NS3, which outlook google sync chokes on. they are extraneous tags and not needed, so I'd like to mark any contacts that contain NS3 with an updated timestamp and flag them as updated in the sync script, strip the NS3 tags or modify to include appropriate XML namespace tags, and then return the updated XML /modify that contact for all users selected in that run, instead of just modifying the incoming XML with the atom client parse string replacement.
  2. I'd like to find a way to synchronize contact photos between accounts - is this possible?

On Fri, Jul 10, 2015 at 6:24 PM, Daniel Schwen notifications@github.com wrote:

I saw @dkelley044 https://github.com/dkelley044 had already implemented a working version of this. I changed the directores and the README a bit.

— Reply to this email directly or view it on GitHub https://github.com/michael-adler/sync-google-contacts/issues/10#issuecomment-120559580 .

mrmattwilkins commented 8 years ago

Hi there, Are you still maintaining this? I hope so, because I have patched it up so google-contacts-sync now works with oauth2! AFAIK this is the only open source freely available bit of code that can sync google contacts. I tried ASynk and it was a buggy. So could you roll in the patch? There is also an extra doco file to help with setting up credentials. README-google-oauth2.txt patch.txt

mrmattwilkins commented 8 years ago

Just a small update on the READ-google-oauth2.txt file. The keyfile and credfile options must be full path names

dschwen commented 8 years ago

Uuuaaahhhh! Thank you! I took a stab at this two weeks ago and have up. The state of Google oauth documentation one of the most frustrating development experiences I've had in a long time.

On Sun, Jun 5, 2016, 2:28 AM mrmattwilkins notifications@github.com wrote:

Just a small update on the READ-google-oauth2.txt file. The keyfile and credfile options must be full path names

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/michael-adler/sync-google-contacts/issues/10#issuecomment-223799907, or mute the thread https://github.com/notifications/unsubscribe/AAMWPko92sprVn88KPpkJoV-qe7Dw_XHks5qIojHgaJpZM4FWcDD .

dkelley044 commented 8 years ago

I've been running it daily for 15+ accounts and 2000+ contacts and it seems to be working. Please bear in mind I originally wrote my oauth2 patch to run on a headless server, hence why the original oauth2 prompts output to shell/console the URL for verification and wait for input of verification key. I haven't had any issues with having to re-authorize after initial setup.

On Sun, Jun 5, 2016 at 9:30 AM, Daniel Schwen notifications@github.com wrote:

Uuuaaahhhh! Thank you! I took a stab at this two weeks ago and have up. The state of Google oauth documentation one of the most frustrating development experiences I've had in a long time.

On Sun, Jun 5, 2016, 2:28 AM mrmattwilkins notifications@github.com wrote:

Just a small update on the READ-google-oauth2.txt file. The keyfile and credfile options must be full path names

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/michael-adler/sync-google-contacts/issues/10#issuecomment-223799907 , or mute the thread < https://github.com/notifications/unsubscribe/AAMWPko92sprVn88KPpkJoV-qe7Dw_XHks5qIojHgaJpZM4FWcDD

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/michael-adler/sync-google-contacts/issues/10#issuecomment-223822645, or mute the thread https://github.com/notifications/unsubscribe/AMKqFETCp0zfxSZdsoHgJ8qN4YrFgsTuks5qIvmVgaJpZM4FWcDD .

David Kelley

Independent Technology Consultant - dkelley044@gmail.com

mrmattwilkins commented 8 years ago

Yeah I agree: oauth2, what a nightmare! In the end I didn't have to add much code at all, it just took forever to find doco that was up to date with a nice example.

On Mon, Jun 6, 2016 at 5:47 AM, David Kelley notifications@github.com wrote:

I've been running it daily for 15+ accounts and 2000+ contacts and it seems to be working. Please bear in mind I originally wrote my oauth2 patch to run on a headless server, hence why the original oauth2 prompts output to shell/console the URL for verification and wait for input of verification key. I haven't had any issues with having to re-authorize after initial setup.

On Sun, Jun 5, 2016 at 9:30 AM, Daniel Schwen notifications@github.com wrote:

Uuuaaahhhh! Thank you! I took a stab at this two weeks ago and have up. The state of Google oauth documentation one of the most frustrating development experiences I've had in a long time.

On Sun, Jun 5, 2016, 2:28 AM mrmattwilkins notifications@github.com wrote:

Just a small update on the READ-google-oauth2.txt file. The keyfile and credfile options must be full path names

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/michael-adler/sync-google-contacts/issues/10#issuecomment-223799907

, or mute the thread <

https://github.com/notifications/unsubscribe/AAMWPko92sprVn88KPpkJoV-qe7Dw_XHks5qIojHgaJpZM4FWcDD

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/michael-adler/sync-google-contacts/issues/10#issuecomment-223822645 , or mute the thread < https://github.com/notifications/unsubscribe/AMKqFETCp0zfxSZdsoHgJ8qN4YrFgsTuks5qIvmVgaJpZM4FWcDD

.

David Kelley Superintendent @ PROBuild Contractors, LLC - dkelley@probuildor.com Independent Technology Consultant - dkelley044@gmail.com (503) 405-6500

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/michael-adler/sync-google-contacts/issues/10#issuecomment-223826740, or mute the thread https://github.com/notifications/unsubscribe/AKpf9xmpWCSmCzStEC-FXje8attP-SThks5qIwufgaJpZM4FWcDD .

michael-adler commented 4 years ago

Finally committed the change to support OAuth

mrmattwilkins commented 4 years ago

Awesome better later than never! Thanks.

On 30/05/2020, at 3:58 AM, Michael Adler notifications@github.com wrote:

 Closed #10.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.