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

[Anthony Nadalin]

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-native-apps/attachments/20140228/65142c20/attachment.html>