Return-Path: 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 73F65132A1E for ; Wed, 23 Aug 2017 15:21:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mJpnHyyjwYw4 for ; Wed, 23 Aug 2017 15:21:49 -0700 (PDT) Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C966D1321C8 for ; Wed, 23 Aug 2017 15:21:48 -0700 (PDT) Received: by mail-vk0-x234.google.com with SMTP id r199so4902109vke.4 for ; Wed, 23 Aug 2017 15:21:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=0DOY7ab+YBjhlgTHkwsAgAaIC3jS7xx4P8U2Oex5x1E=; b=mS4SE+UsjN7lPStcjdLAYuHaCleIoskIrs3cwztlMq/RyKjExdf/9+y2T+GNagm7Ax PbdFlWw5SWpjaugK/ORMRcB+70jQuABlLfRwfvuYjst3wOvT4YTPkCU1Dw0mY+x4Za8I dWDywpnokslUkuytE5ZvP47sL8lc1shwWgNeR6SDEOJgEnorrrcJkXSeKlCoFKRPmNGv 68+cgWmr87vFZedbXIPhsX7rqmLzF+G2c7vkQSYNG6qEkRhqcJq5VVEkaZOzZwoJs7jx RK5Gbv/OJC7asfIllSJoeZSysHHaXR+IEtUvc1wCL9hQmF8rrqZ09gn1B3E3AqMCbIxM LQ2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0DOY7ab+YBjhlgTHkwsAgAaIC3jS7xx4P8U2Oex5x1E=; b=DmsLLr65Oqfns0e0ZG1cTnuB0DRar0xqAg6UIK1kWdTovyWwiooLiuy/mt7hbYvsth BQz/8X5likfe1u9PZgdpEsXw4eBhTyIj8mF8U9C1A8/k7UVO0y1W2lIct8k8IdriU/I+ znkGS50I9lQuizFbbT5ydsQ46ptfSBwm+jpeJFQf3wzta+V1cn+H+BSh+iCzhD9b2EAA /ZIJJwc7PK6R0wGLWwcZgXUc8cUF9QRmmiwCdyIT9OaF0JfQdl/P18Eo86qzjW6gME3P e45lcy0ET05cmi4OR95cgc8EUr8GDp+Jp01B7B9Qes3V0qZPiiL854AOt6NiwGFY43Mj M2WQ== X-Gm-Message-State: AHYfb5hzjd/7S+5CHbhiOKwLeYVnATwyGQxCBuR7yL2hcBiWrmCSNnYf tuRtE6rYgVMBkEonYboAgimAu9gbRw== X-Received: by 10.31.96.149 with SMTP id u143mr3106607vkb.101.1503526907616; Wed, 23 Aug 2017 15:21:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.93.47 with HTTP; Wed, 23 Aug 2017 15:21:47 -0700 (PDT) From: Malla Simhachalam Date: Wed, 23 Aug 2017 15:21:47 -0700 Message-ID: To: oauth@ietf.org Content-Type: multipart/alternative; boundary="001a114e5fec3d23b70557732358" Archived-At: Subject: [OAUTH-WG] Obtaining authorized scopes X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2017 22:21:50 -0000 --001a114e5fec3d23b70557732358 Content-Type: text/plain; charset="UTF-8" Hi, We have an OAuth token revocation specification to revoke consents from an external/relying party with a given token. I am wondering if there's a specification around retrieving granted scopes using a given token for external relying party. thanks Malla --001a114e5fec3d23b70557732358 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

We have an OAuth token rev= ocation specification to revoke consents from an external/relying party wit= h a given token. I am wondering if there's a specification around retri= eving granted scopes using a given token for external relying party.
thanks
Malla
--001a114e5fec3d23b70557732358--