Return-Path: X-Original-To: apmail-incubator-amber-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-amber-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2C561E128 for ; Mon, 14 Jan 2013 12:54:15 +0000 (UTC) Received: (qmail 25251 invoked by uid 500); 14 Jan 2013 12:54:14 -0000 Delivered-To: apmail-incubator-amber-dev-archive@incubator.apache.org Received: (qmail 24317 invoked by uid 500); 14 Jan 2013 12:54:13 -0000 Mailing-List: contact amber-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: amber-dev@incubator.apache.org Delivered-To: mailing list amber-dev@incubator.apache.org Received: (qmail 24278 invoked by uid 99); 14 Jan 2013 12:54:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2013 12:54:13 +0000 Date: Mon, 14 Jan 2013 12:54:12 +0000 (UTC) From: "Antonio Sanso (JIRA)" To: amber-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBER-70) Extend the client library in order to easily handle bearer token request MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso resolved AMBER-70. -------------------------------- Resolution: Fixed Fix Version/s: 0.23 fixed in rev. 1432904 > Extend the client library in order to easily handle bearer token request > ------------------------------------------------------------------------ > > Key: AMBER-70 > URL: https://issues.apache.org/jira/browse/AMBER-70 > Project: Amber > Issue Type: Improvement > Reporter: Antonio Sanso > Fix For: 0.23 > > > At the moment once obtained the access token there is not help from the library to request a resource using the token. E,g, the client demo does manually > URL url = new URL( > oauthParams.getResourceUrl() + "?" + tokenName + "=" + oauthParams.getAccessToken()); > It would be nice to extend the client in order to accommodate the 3 kind of bearer requests as for spec [0] > [0] http://tools.ietf.org/html/rfc6750#section-2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira