Re: [OAUTH-WG] 2 Leg with OAuth 2.0

Brian Campbell <bcampbell@pingidentity.com> Tue, 29 November 2011 20:13 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA161F0CA4 for <oauth@ietfa.amsl.com>; Tue, 29 Nov 2011 12:13:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level:
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LmXHWWzIIDaL for <oauth@ietfa.amsl.com>; Tue, 29 Nov 2011 12:13:08 -0800 (PST)
Received: from na3sys009aog101.obsmtp.com (na3sys009aog101.obsmtp.com [74.125.149.67]) by ietfa.amsl.com (Postfix) with ESMTP id 74CB41F0C82 for <oauth@ietf.org>; Tue, 29 Nov 2011 12:13:08 -0800 (PST)
Received: from mail-gy0-f173.google.com ([209.85.160.173]) (using TLSv1) by na3sys009aob101.postini.com ([74.125.148.12]) with SMTP ID DSNKTtU809CwD6DK83qVUZHn1PumDTu2vQuz@postini.com; Tue, 29 Nov 2011 12:13:08 PST
Received: by mail-gy0-f173.google.com with SMTP id g19so8863280ghb.18 for <oauth@ietf.org>; Tue, 29 Nov 2011 12:13:07 -0800 (PST)
Received: by 10.236.114.195 with SMTP id c43mr73921519yhh.12.1322597587789; Tue, 29 Nov 2011 12:13:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.146.192.35 with HTTP; Tue, 29 Nov 2011 12:12:36 -0800 (PST)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723452856C6DBE@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <CAK04b078ohKScZWEd-fJpiO73GFP-fOd+Lu8su-_nZs_KrKgbg@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723452856C6DBE@P3PW5EX1MB01.EX1.SECURESERVER.NET>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Tue, 29 Nov 2011 13:12:36 -0700
Message-ID: <CA+k3eCSS9yKw_WmeWrwZhkVsZS=XvHe0Y14tgwNmV49_hvQHjA@mail.gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] 2 Leg with OAuth 2.0
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2011 20:13:09 -0000

Or using the SAML or JWT grants to get an access token, then using the
protocol as usual.


On Tue, Nov 29, 2011 at 1:06 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> This functionality can be implemented in two main ways:
>
>
>
> 1.       Using the client credentials flow to get an access token, then
> using the protocol as usual
>
> 2.       Just using the Bearer (over SSL) or MAC token schemes without the
> rest of OAuth
>
>
>
> EHL
>
>
>
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of
> Brian Hawkins
> Sent: Tuesday, November 29, 2011 11:49 AM
> To: oauth@ietf.org
> Subject: [OAUTH-WG] 2 Leg with OAuth 2.0
>
>
>
> I'm having trouble finding information on how to do 2leg authentication with
> OAuth 2.0.  Does it even support it?
>
>
>
> Thanks
>
> Brian
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>