[Openid-specs-native-apps] Native Apps discussion at RSA

Paul Madsen paul.madsen at gmail.com
Fri Feb 28 18:04:06 UTC 2014


Tony, go ahead & do with this 'standard oauth', I wish you the best of 
luck

Others agree that there are additional requirements, and value in 
standardizing them

What is the cost to you if you don't participate? I imagine we would 
muddle along quite happily without you

paul


On Fri Feb 28 12:52:24 2014, Anthony Nadalin wrote:
> Why, it will be yo to server to understand trust aspects and it will
> be standard oauth protocols. The platform brokers will be default so
> what us value of this effort?
>
> Sent from my Windows Phone
> ------------------------------------------------------------------------
> From: Paul Madsen <mailto:paul.madsen at gmail.com>
> Sent: ‎2/‎28/‎2014 9:44 AM
> To: Anthony Nadalin <mailto:tonynad at microsoft.com>; Mike Jones
> <mailto:Michael.Jones at microsoft.com>; Ashish Jain
> <mailto:ashishjain at vmware.com>; Sean Ginevan
> <mailto:sginevan at mobileiron.com>; ErichStuntebeck at air-watch.com
> <mailto:erichstuntebeck at air-watch.com>; thomas.debenning at onelogin.com
> <mailto:thomas.debenning at onelogin.com>; Blake Brannon
> <mailto:blakebrannon at air-watch.com>; Caleb Baker
> <mailto:Caleb.Baker at microsoft.com>
> Cc: openid-specs-native-apps at lists.openid.net
> <mailto:openid-specs-native-apps at lists.openid.net>
> Subject: Re: [Openid-specs-native-apps] Native Apps discussion at RSA
>
> We are defining that 'well understood protocol '
>
> if you see no value in participating, don't
>
> Paul
>
> Anthony Nadalin <tonynad at microsoft.com> wrote:
>
> Bottom line here is that the platform vendors are going to build the
> brokers and they will expose APIs and as long as they use a understood
> protocol there is really no need to have this standardized.
>
> *From:* openid-specs-native-apps-bounces at lists.openid.net
> [mailto:openid-specs-native-apps-bounces at lists.openid.net] *On Behalf
> Of *Mike Jones
> *Sent:* Thursday, February 27, 2014 7:57 PM
> *To:* Ashish Jain; Sean Ginevan; ErichStuntebeck at air-watch.com;
> thomas.debenning at onelogin.com; Blake Brannon; Caleb Baker
> *Cc:* openid-specs-native-apps at lists.openid.net
> *Subject:* [Openid-specs-native-apps] Native Apps discussion at RSA
>
> Attendees:
>
> Ashish Jain
>
> Sean Ginevan
>
> Erich Stuntebeck
>
> Thomas DeBenning
>
> Blake Brannon
>
> Caleb Baker
>
> Mike Jones
>
> We discussed the status of the specs, goals, interop and adoption.
>
> Mike asked questions like:
>
>                What problem is this trying to solve?
>
>                Who will deploy this middleware?  Platform vendors?
>
>                What does success look like?
>
> Ashish said that building the ecosystem requires the participation of
> three parties:
>
>                Identity Providers
>
>                Enterprise Mobility Management (EMM) Vendors (such as
> AirWatch, Mobile Island)
>
>                Application Developers / SAAS Vendors
>
> We asked why there is the list of applications required in the specs
>
> The enterprise use cases require federation, which may make them more
> compelling than consumer use cases, at least at first
>
> Apparently there is a deck from the most recent CIS that outlines use
> cases and gives an overview
>
>                By Ashish, Paul Madsen, Josh
>
>                Caleb and Mike asked this to be shared
>


More information about the Openid-specs-native-apps mailing list