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

[John Bradley]

I was at the meeting meeting where the GSMA drafted the charter.   There is interest in eventually using napps and perhaps contributing to it. 

However the focus of Mobile Connect WG is mobile operators and not mobile devices, and will focus creating a common profile for MNO to provide a consistent openID provider service.

There are MNO specific questions around discovery of a IdP based on phone number, and how to register clients.  There is some desire to allow RP/Clients to consent once to a TOS that enables them to connect to any MNO.   It might be that it is a single client_id or registration token that is used.

I don't think there is any intent to overlap.

John B.

On Mar 17, 2014, at 6:54 PM, Ashish Jain <ashishjain at vmware.com> wrote:

> Mike  - Do you have any information if the MobileConnect working group charter has any overlap / similarities with this group ?
> -- Ashish 
> 
> From: "Mike Jones" <Michael.Jones at microsoft.com>
> To: "Ashish Jain" <ashishjain at vmware.com>, "Sean Ginevan" <sginevan at mobileiron.com>, "ErichStuntebeck at air-watch.com" <erichstuntebeck at air-watch.com>, "thomas debenning" <thomas.debenning at onelogin.com>, "Blake Brannon" <blakebrannon at air-watch.com>, "Caleb Baker" <Caleb.Baker at microsoft.com>
> Cc: openid-specs-native-apps at lists.openid.net
> Sent: Thursday, February 27, 2014 7:56:34 PM
> Subject: 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
>  
> 
> _______________________________________________
> Openid-specs-native-apps mailing list
> Openid-specs-native-apps at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-native-apps

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-native-apps/attachments/20140317/b7047dc5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4507 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-native-apps/attachments/20140317/b7047dc5/attachment-0001.p7s>