[OAUTH-WG] Examples of structured tokens in the wild?

Aaron Parecki <aaron@parecki.com> Sun, 25 March 2012 17:51 UTC

Return-Path: <aaron@parecki.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 ACD6521F847E for <oauth@ietfa.amsl.com>; Sun, 25 Mar 2012 10:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.755
X-Spam-Level:
X-Spam-Status: No, score=-2.755 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 MC3YlUC2a7UM for <oauth@ietfa.amsl.com>; Sun, 25 Mar 2012 10:51:04 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3A82C21F847C for <oauth@ietf.org>; Sun, 25 Mar 2012 10:51:04 -0700 (PDT)
Received: by pbbrq13 with SMTP id rq13so5121056pbb.31 for <oauth@ietf.org>; Sun, 25 Mar 2012 10:51:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=AGCcyboPSuGOoLxY3Zb+2OtXd/pIvMfFYu3iQoH3Tp0=; b=kWg76cTyybzL7S4AXBWfRiIEPJLKEqAVVUQgQDmQ0BipQBk3xxPWFl/qv+lLP8jAA9 /lHx3aZbwgnCnoaUzprWdwbp+PuBxOuI2K40JPVMyyvKwZeTrjpt2H1gZf1/EbhQe4mE khbjdTHd6c1IopKPJ3DyUuXl83PyH7FIbF7HKW6sVYkzgbz+yervcOfUPE6nYKwdK5S6 8tRq3mc+HMMNQPSeVy8eIFUpG631Hps9FsEduxj7JP7u7b6NAeqULJlTafOqW4jc0SFm bcwDgaGXURLtsDOZGHh3cGM/AeugXJUYRqmup1BFp+iT45krr2pfBzV4FITrrQZTyJKf Nlaw==
Received: by 10.68.212.35 with SMTP id nh3mr24016014pbc.84.1332697864030; Sun, 25 Mar 2012 10:51:04 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by mx.google.com with ESMTPS id b4sm10631446pbc.7.2012.03.25.10.51.02 (version=SSLv3 cipher=OTHER); Sun, 25 Mar 2012 10:51:03 -0700 (PDT)
Received: by pbbrq13 with SMTP id rq13so5121040pbb.31 for <oauth@ietf.org>; Sun, 25 Mar 2012 10:51:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.129.74 with SMTP id nu10mr46256322pbb.157.1332697862251; Sun, 25 Mar 2012 10:51:02 -0700 (PDT)
Received: by 10.143.90.17 with HTTP; Sun, 25 Mar 2012 10:51:02 -0700 (PDT)
Date: Sun, 25 Mar 2012 10:51:02 -0700
Message-ID: <CAGBSGjooYABosErTDe=6XQp0Y8pCWu+GasFj6JdDtg_NA8UMfw@mail.gmail.com>
From: Aaron Parecki <aaron@parecki.com>
To: OAuth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="e89a8f234f31ac253b04bc14e6a6"
X-Gm-Message-State: ALoCoQmmn3jb5dBDjoQfvZdgz6O8ySDv7/r3L8RB2ceMBmcpWpcKm4e4dxTVQ2FRq78dufBUFZms
Subject: [OAUTH-WG] Examples of structured tokens in the wild?
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, 25 Mar 2012 17:51:04 -0000

If you have an example of an API that uses structured access tokens, I
would love some links to documentation or examples. I'm looking for some
examples of the types of information people put into structured tokens for
some OAuth 2 tutorials I'm writing. It would be great if these examples
were available in public services that I could poke at as well.

Thanks!

Aaron Parecki