Allow read-only access via a calendar's "private address" URL

[GoogleCodeExporter]

Each Google calendar has an associated "private address" (available via the
calendar's settings page) -- see
http://www.google.com/support/calendar/bin/answer.py?answer=34576&ctx=tltp
.  In cases where gcalcli is used only for read-only information, it would
be convenient if this URL could be provided, in place of a
username/password, so that the username/pw didn't need to be stored in a
plaintext file.

Original issue reported on code.google.com by edgim...@gmail.com on 12 Jan 2010 at 10:11

[GoogleCodeExporter]

Ok, I've patched the code to do this...  It's not overly pretty, and doesn't do 
any
kind of checking for write commands when using a magic-url, but it works.  
(patch is
attached)

Original comment by edgi...@gmail.com on 12 Jan 2010 at 9:29

Attachments:

• magic_cookie_authentication.patch

[GoogleCodeExporter]

I've since made a couple additional changes (better documentation, etc.) to this
patch.  In case anyone is interested in trying the patched version, you can get 
it at
my personal gcalcli repository -- http://bitbucket.org/edgimar/gcalcli/ .

Original comment by edgi...@gmail.com on 17 Jan 2010 at 7:33

[GoogleCodeExporter]

Thank you for your patch.  I'll be integrating it soon as well as examining 
what you did in your fork on bitbucket.

Original comment by eda...@insanum.com on 28 Jul 2011 at 12:43

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by eda...@insanum.com on 11 Aug 2011 at 6:59

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I think this is a good idea but no traction.

gcalcli has moved to github: https://github.com/insanum/gcalcli

If you'd like to see this work progress please file a new issue over there... 
or fork/code and submit a pull request.  :-)

Original comment by eda...@insanum.com on 15 May 2012 at 3:03

• Changed state: WontFix