From: David Engster <deng@randomsample.de>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org, Stephen Eglen <sje30@cam.ac.uk>
Subject: Re: org-caldav: Sync Org with external calendars through CalDAV (Owncloud, Google, ...)
Date: Tue, 04 Dec 2012 20:27:22 +0100 [thread overview]
Message-ID: <87y5hdr52d.fsf@engster.org> (raw)
In-Reply-To: <20121204102904.GA4294@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Tue, 4 Dec 2012 11:29:04 +0100")
Suvayu Ali writes:
> On Mon, Dec 03, 2012 at 08:50:35PM +0100, David Engster wrote:
>> I'm at a loss why this happens, and I could not reproduce it with my
>> account. This problem really has nothing to do with org-caldav, since it
>> is delegating this part to the url package. As I've already written to
>> Bastien, please try
>>
>> (url-retrieve-synchronously
>> "https://www.google.com/calendar/dav/YOUR-CALENDAR-ID@group.calendar.google.com/events/")
>>
>> If this doesn't ask for your username, then there's your
>> problem. Depending on the Emacs version you're using, you might want to
>> set
>>
>> (setq auth-source-debug t)
>>
>> to see whether some .netrc file or similar is setting the username for
>> you (look into the *Messages* buffer).
>>
>
> I see the same issue, I get only a password prompt. This is what I get
> on trying your suggestion above.
>
> Contacting host: www.google.com:443
> auth-source-search: found 1 results (max 1) matching (:max 1 :host
> "www.google.com:443" :port "https")
> auth-source-search: found 1 CACHED results matching (:max 1 :host
> "www.google.com:443" :port "https")
> #<buffer *http www.google.com:443*-771021>
>
> I'm not sure from this if my netrc is being used.
Yes. The mesage "found 1 results" means it found an entry in your .netrc
or .authinfo which matches.
> My netrc also has the password for my Google account, if it is being
> used should I even get a password prompt?
The auth-source stuff can be a bit tricky. For https connections with
the URL package, you need to use the following
machine www.google.com:443 port https login USERNAME password PASS
That's no typo: You have to use ":443" as well as "port https". See also
(info "(auth)Help for users")
-David
next prev parent reply other threads:[~2012-12-04 19:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 19:12 org-caldav: Sync Org with external calendars through CalDAV (Owncloud, Google, ...) David Engster
2012-07-20 16:36 ` David Engster
2012-07-20 16:55 ` Mehul Sanghvi
2012-07-20 18:00 ` Jason F. McBrayer
[not found] ` <deng@randomsample.de>
2012-07-20 18:29 ` Nick Dokos
2012-07-23 19:25 ` Suvayu Ali
2012-07-26 17:10 ` Aurélien Aptel
2012-07-25 8:18 ` Torsten Wagner
2012-07-25 19:02 ` David Engster
2012-07-27 14:49 ` Torsten Wagner
2012-07-28 12:05 ` David Engster
2012-08-03 7:46 ` Bastien
2012-08-03 12:48 ` David Engster
2012-08-04 8:27 ` Bastien
2012-08-05 18:41 ` David Engster
2012-12-03 12:35 ` Stephen Eglen
2012-12-03 19:50 ` David Engster
2012-12-04 10:29 ` Suvayu Ali
2012-12-04 10:45 ` Stephen Eglen
2012-12-04 11:19 ` Stephen Eglen
2012-12-04 19:19 ` David Engster
2012-12-05 11:40 ` Stephen Eglen
2012-12-05 12:15 ` Stephen Eglen
2012-12-04 19:27 ` David Engster [this message]
2012-09-11 14:17 ` Philipp Haselwarter
-- strict thread matches above, loose matches on Subject: below --
2012-07-26 16:43 Robert Eckl
2012-07-26 19:03 ` David Engster
2012-07-26 20:55 ` David Engster
2012-07-30 2:01 ` Luis Anaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5hdr52d.fsf@engster.org \
--to=deng@randomsample.de \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.com \
--cc=sje30@cam.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).