Re: [OAUTH-WG] Deutsche Telekom launched OAuth 2.0 support

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Fri, 01 July 2011 21:53 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 5C18D11E81C3 for <oauth@ietfa.amsl.com>; Fri, 1 Jul 2011 14:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHgSPAY1RHV8 for <oauth@ietfa.amsl.com>; Fri, 1 Jul 2011 14:53:14 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id C879F11E8188 for <oauth@ietf.org>; Fri, 1 Jul 2011 14:53:14 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p61LrDXA017118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <oauth@ietf.org>; Fri, 1 Jul 2011 16:53:14 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p61LrDmq019638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <oauth@ietf.org>; Fri, 1 Jul 2011 16:53:13 -0500
Received: from [135.222.134.156] (USMUYN0L055118.mh.lucent.com [135.222.134.156]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p61LrD56008750; Fri, 1 Jul 2011 16:53:13 -0500 (CDT)
Message-ID: <4E0E41C9.3090608@alcatel-lucent.com>
Date: Fri, 01 Jul 2011 17:53:13 -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: <4E0E39EA.7040809@lodderstedt.net>
In-Reply-To: <4E0E39EA.7040809@lodderstedt.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [OAUTH-WG] Deutsche Telekom launched OAuth 2.0 support
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: Fri, 01 Jul 2011 21:53:15 -0000

Torsten,

With many thanks for the note, I think it would be great if you 
documented the implementation report in an Informational RFC.  In 
particular, the SIM-based authentication part is of particular interest 
here--we had this discussion on this list recently-- as it naturally 
extends the use of the Internet protocols in the telecom environment.

I also think that such an implementation report would influence 
positively  the OAuth profiling work that is taking  place in ITU-T, OMA 
and other places.

Igor

On 7/1/2011 5:19 PM, Torsten Lodderstedt wrote:
> Hi all,
>
> I would like to announce that we recently launched OAuth 2.0 support 
> in our Security Token Service. It will be used in upcoming consumer 
> products (e.g. Smartphone apps).
>
> The current implementation supports draft 10 (but is also inline with 
> the latest text on native apps). It has the following additional 
> features:
> - Issuance of multiple tokens for different services in single 
> authorization process (Bulk User Authorization)
> - Token revocation 
> (http://datatracker.ietf.org/doc/draft-lodderstedt-oauth-revocation/)
> - custom grant types for token exchange and SIM card authentication
> - Token replacement
> - Parameter to explicitely request refresh token for "Resource Owner 
> Password Credentials" grant type
>
> regards,
> Torsten.
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth