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

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Mon, 19 March 2012 18:11 UTC

Return-Path: <igor.faynberg@alcatel-lucent.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 9419721F87B0 for <oauth@ietfa.amsl.com>; Mon, 19 Mar 2012 11:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.562
X-Spam-Level:
X-Spam-Status: No, score=-7.562 tagged_above=-999 required=5 tests=[AWL=-0.963, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 gSIuPFQZmz91 for <oauth@ietfa.amsl.com>; Mon, 19 Mar 2012 11:11:30 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 064BD21F8489 for <oauth@ietf.org>; Mon, 19 Mar 2012 11:11:29 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q2JIBRUX013099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <oauth@ietf.org>; Mon, 19 Mar 2012 13:11:27 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q2JIBRma015551 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <oauth@ietf.org>; Mon, 19 Mar 2012 13:11:27 -0500
Received: from [135.222.232.245] (USMUYN0L055118.mh.lucent.com [135.222.232.245]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q2JIBQaT017162; Mon, 19 Mar 2012 13:11:27 -0500 (CDT)
Message-ID: <4F6776E9.2000902@alcatel-lucent.com>
Date: Mon, 19 Mar 2012 14:11:53 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: oauth@ietf.org
References: <1db661c5-2e54-470e-8104-ee8e7ae10e86@default> <A8BFFBB5-9912-468C-AB42-702DA368D59F@oracle.com> <12509c43-163e-43a6-bbf3-60d6daa1db43@default> <FB4F059C-6E02-4240-98A6-069CCA700186@gmx.net> <835C2B6E-3A48-4894-A75E-B802FB12DD1C@oracle.com>
In-Reply-To: <835C2B6E-3A48-4894-A75E-B802FB12DD1C@oracle.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: Re: [OAUTH-WG] Using Oauth2 token to SOAP web services
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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 18:11:31 -0000

Phil is right!  I observe the same thing: the frond-end is RESTful; the 
back-end is mixed.  Personally, I think it would be good for OAuth to be 
deployed as wide as possible.  (The SAML/OAuth  ideas I think are 
working the same problem.)

Igor

On 3/19/2012 9:23 AM, Phil Hunt wrote:
> There's going to be a lot of mixed environments for some time. Particularly an issue at the boundaries between classic soap services and new restful services.
>
> Phil
>
> On 2012-03-19, at 0:05, Hannes Tschofenig<hannes.tschofenig@gmx.net>  wrote:
>
>> 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
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth