From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: OAuth2 implementation in Elisp
Date: Mon, 26 Sep 2011 09:36:44 -0500 [thread overview]
Message-ID: <87y5xb4bgj.fsf@lifelogs.com> (raw)
In-Reply-To: 87vcsfmxzd.fsf@keller.adm.naquadah.org
On Mon, 26 Sep 2011 11:52:54 +0200 Julien Danjou <julien@danjou.info> wrote:
>> That makes no sense. You are asking the user to enter information Emacs
>> is displaying. Can you grab that information for them, so they don't
>> have to enter it?
JD> No, this would kill the whole point of OAuth. You may want to take a
JD> look at the spec of the protocol to understand how it works. :)
On Sun, 25 Sep 2011 13:50:05 -0700 Justin Lilly <justin@justinlilly.com> wrote:
JL> w/r/t the entering a string, this is part of how oauth2 works for
JL> desktop applications. The other workflow is for web apps specifically.
JL> Familiarizing yourself with the spec might make reviewing the code a
JL> bit more sane as it should clear up some of these ambiguities.
Why can't Emacs behave like a web app?
I used OAuth 1 which had a similarly annoying feature. It made it very
unlikely for users to try my code and I got many bug reports. So I hope
we can avoid it.
The OAuth 2 spec (I found it at http://tools.ietf.org/html/draft-ietf-oauth-v2-22)
seems to provide for a seamless experience where the user authenticates
against a server and then the security code is fed back to the client
application through a redirect. Perhaps I'm misunderstanding the flow;
my question is simply "if there's information Emacs knows, can you
please avoid asking the user to retype it?"
I hope I don't have to know how to implement OAuth2 in order to
understand your answer to that question.
Ted
next prev parent reply other threads:[~2011-09-26 14:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 21:55 OAuth2 implementation in Elisp Julien Danjou
2011-09-22 21:59 ` Deniz Dogan
2011-09-22 22:00 ` Deniz Dogan
2011-09-22 22:15 ` Julien Danjou
2011-09-25 11:25 ` Ted Zlatanov
2011-09-25 12:56 ` Julien Danjou
2011-09-25 13:31 ` Ted Zlatanov
2011-09-25 17:14 ` Karl Fogel
2011-09-25 20:50 ` Justin Lilly
2011-09-26 9:52 ` Julien Danjou
2011-09-26 14:36 ` Ted Zlatanov [this message]
2011-09-26 15:04 ` Julien Danjou
2011-09-26 15:15 ` Lars Magne Ingebrigtsen
2011-09-26 15:17 ` Julien Danjou
2011-09-26 16:24 ` Lars Magne Ingebrigtsen
2011-09-27 9:40 ` Julien Danjou
2011-09-27 23:25 ` Richard Stallman
2011-09-26 17:47 ` joakim
2011-09-26 19:09 ` Ted Zlatanov
2011-09-26 19:55 ` Tassilo Horn
2011-09-26 19:59 ` Lars Magne Ingebrigtsen
2011-09-26 20:29 ` Tassilo Horn
2011-09-26 20:31 ` Lars Magne Ingebrigtsen
2011-09-26 21:26 ` Ted Zlatanov
2011-09-27 9:43 ` Julien Danjou
2011-09-27 9:50 ` joakim
2011-09-27 10:14 ` Ted Zlatanov
2011-09-27 12:22 ` joakim
2011-09-27 20:17 ` Ted Zlatanov
2011-09-26 17:00 ` Ted Zlatanov
2011-09-28 3:35 ` Vijay Lakshminarayanan
2011-09-26 21:23 ` Ted Zlatanov
2011-09-27 10:18 ` Ted Zlatanov
2011-09-27 11:42 ` Julien Danjou
2011-09-27 20:20 ` Ted Zlatanov
2011-09-25 20:02 ` Deniz Dogan
2011-09-23 4:34 ` Stefan Monnier
2011-09-23 7:31 ` Julien Danjou
2011-09-23 8:23 ` Andreas Röhler
2011-09-23 8:48 ` Michael Albinus
2011-09-23 9:02 ` Julien Danjou
2011-09-23 9:32 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5xb4bgj.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.