Re: [OAUTH-WG] Using Oauth2 token to SOAP web services

Hannes Tschofenig <hannes.tschofenig@gmx.net> Mon, 19 March 2012 07:05 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 EB3AD21F84F5 for <oauth@ietfa.amsl.com>; Mon, 19 Mar 2012 00:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level:
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 xk+zmIWRnCRc for <oauth@ietfa.amsl.com>; Mon, 19 Mar 2012 00:05:44 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 7403921F84F2 for <oauth@ietf.org>; Mon, 19 Mar 2012 00:05:44 -0700 (PDT)
Received: (qmail invoked by alias); 19 Mar 2012 07:05:42 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.107]) [88.115.216.191] by mail.gmx.net (mp019) with SMTP; 19 Mar 2012 08:05:42 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18UyncJ3T0UJlcDOUvSbr1xCPobEvM437BeUEKsmy xVnuRyPqNfLJxN
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="windows-1252"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Priority: 3
In-Reply-To: <12509c43-163e-43a6-bbf3-60d6daa1db43@default>
Date: Mon, 19 Mar 2012 09:05:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB4F059C-6E02-4240-98A6-069CCA700186@gmx.net>
References: <1db661c5-2e54-470e-8104-ee8e7ae10e86@default> <A8BFFBB5-9912-468C-AB42-702DA368D59F@oracle.com> <12509c43-163e-43a6-bbf3-60d6daa1db43@default>
To: Grant Yang <guang.g.yang@oracle.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Using Oauth2 token to SOAP web services
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: Mon, 19 Mar 2012 07:05:46 -0000

Hi Grant, 

IMHO the main reason why the OAuth specification does not standardize OAuth usage specially for SOAP is because most people by now realized that SOAP, as another layer of encapsulation, does not add a lot of value. 

Ciao
Hannes

On Mar 19, 2012, at 6:15 AM, Grant Yang wrote:

> Thank you very much Phil!
>  
> The thing is, the Oauth spec just mentioned putting the Access Token into HTTP header “Authorization”. I don’t think it applies to SOAP as this header is not visible from SOAP stack perspective.
>  
> So, when we talking about the soap header, are we talking about the header used by WS-Security? Could you please be kindly providing me one example on putting the Access Token into SOAP header and let me know which product is currently using this mechanism?
>  
> Thanks a lot,
> Grant.
>  
> From: Phil Hunt 
> Sent: Thursday, March 15, 2012 11:53 PM
> To: Grant Yang
> Subject: Re: [OAUTH-WG] Using Oauth2 token to SOAP web services
>  
> Grant,
>  
> You put it in the soap header of course in the same spot as any other credential.  :-)
>  
> Phil
>  
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
> 
>  
> 
> 
>  
> On 2012-03-14, at 10:41 PM, Grant Yang wrote:
> 
> 
> Hi all,
>  
> We were discussing the possibility to use Oauth2 token on SOAP in our product.
>  
> The preferred way in mentioned in RFC is of course to put it to HTTP Authorization header, but in this case it will beyond the scope of SOAP stack and I am not sure it shall be the correct way to go. It is also recognized that there is some implementation (such as salesforce) is using some SOAP header (“sessionId”) to put this token, but it looks like a private implementation and I did not find any specification supporting it.
>  
> Could any experts here illustrate any organization or forum is working on using Oauth2 token for SOAP request? As there are quite some legacy SOAP based web services, hopefully it is a question makes sense for you as well.
>  
> Thoughts?
>  
> Grant Yang
> Architect, SDP of ORACLE Communications
>  
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>  
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth