[OAUTH-WG] OAuth mobile flow
Security Developer <security.developer22@gmail.com> Sun, 24 March 2013 19:47 UTC
Return-Path: <security.developer22@gmail.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 367E721F8615 for <oauth@ietfa.amsl.com>; Sun, 24 Mar 2013 12:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 VZW0xOr6tw2o for <oauth@ietfa.amsl.com>; Sun, 24 Mar 2013 12:47:49 -0700 (PDT)
Received: from mail-oa0-f66.google.com (mail-oa0-f66.google.com [209.85.219.66]) by ietfa.amsl.com (Postfix) with ESMTP id AD9D121F860B for <OAuth@ietf.org>; Sun, 24 Mar 2013 12:47:49 -0700 (PDT)
Received: by mail-oa0-f66.google.com with SMTP id n12so776412oag.5 for <OAuth@ietf.org>; Sun, 24 Mar 2013 12:47:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=n0lDJgQXWOi0e1xEKCT/BDuA9IwGPsRO9vp4wCEtpqY=; b=ymz4NK/GoBmSME6gpYMFNXIcI60gBsEc3HXE66NRlYMm4bhR5JRgAWBWK+pbzFtKSG 5moJ0dCifQmDwTNMvGYnvjmzU4xT55VU9RcJvXm5QA/xA1TrdvRm8pg716arUbdPwTnm ROI19y0mjTRIZ9oIgNzqR7C8liXRh7YlYBVkZIa56WqKyz2yAdwcTe1k++u75HLqOm41 kNBFJKEb3zX5r8csaJfenJNTSQSN13u+5ZPw5/vTeLS35Bpz4TTcULmoY2rbGi6LpoiQ EpkOhwZyPXEhWyTCsH7W8AwcgprvMh26HdnLlLeyQHIbxV9htWV6BzAVxVEk/m39MxpB lesA==
MIME-Version: 1.0
X-Received: by 10.60.1.225 with SMTP id 1mr8691357oep.141.1364154469246; Sun, 24 Mar 2013 12:47:49 -0700 (PDT)
Received: by 10.182.79.233 with HTTP; Sun, 24 Mar 2013 12:47:49 -0700 (PDT)
Date: Mon, 25 Mar 2013 00:47:49 +0500
Message-ID: <CAD-drXvL5OqLSwbQfy5HWdKZPmn72-wVPQB2C5gLFgvJ4YcgfA@mail.gmail.com>
From: Security Developer <security.developer22@gmail.com>
To: OAuth@ietf.org
Content-Type: multipart/alternative; boundary="e89a8fb1fbba8f3dcc04d8b0f646"
Subject: [OAUTH-WG] OAuth mobile flow
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: Sun, 24 Mar 2013 19:47:50 -0000
Hi, Can any body please help in describing the OAuth flow for mobile applications? Thanks for your time.
- [OAUTH-WG] OAuth mobile flow Security Developer
- Re: [OAUTH-WG] OAuth mobile flow Shane B Weeden
- Re: [OAUTH-WG] OAuth mobile flow Sergey Beryozkin
- Re: [OAUTH-WG] OAuth mobile flow Brian Campbell
- Re: [OAUTH-WG] OAuth mobile flow Shane B Weeden
- Re: [OAUTH-WG] OAuth mobile flow Justin Richer
- Re: [OAUTH-WG] OAuth mobile flow Sergey Beryozkin
- Re: [OAUTH-WG] OAuth mobile flow Shane B Weeden