[Openid-specs-mobile-profile] Issue #32: Mobile Registration : napps application type (openid/mobile)

Lodderstedt, Torsten t.lodderstedt at telekom.de
Wed Oct 28 00:49:27 UTC 2015

Hi Matthieu,

we just learned at the Internet Identity Workshop that the NAPPS working group changed direction and will no longer propose usage of token agents for native apps. Instead, the recommendation for native apps is to use new browser features (e.g. custom chrome tabs). So we should be fine with using the application types from the OpenID Connect Client registration types (web and native).

kind regards,

-----Ursprüngliche Nachricht-----
Von: Openid-specs-mobile-profile [mailto:openid-specs-mobile-profile-bounces at lists.openid.net] Im Auftrag von Matthieu Verdier
Gesendet: Montag, 26. Oktober 2015 02:47
An: openid-specs-mobile-profile at lists.openid.net
Betreff: [Openid-specs-mobile-profile] Issue #32: Mobile Registration : napps application type (openid/mobile)

New issue 32: Mobile Registration : napps application type https://bitbucket.org/openid/mobile/issues/32/mobile-registration-napps-application-type

Matthieu Verdier:

On the sup^port of "napps" client application type :
The point I was trying to make with regard to Modrna registration issues  is that Modrna is agnostic to the Client Application Type, at least for the two application types defined in Openid Connect Dynamic Registration 1.0.
The default type for Modrna should be “web”. But there is no counter indication of using a “napps” application type if the Modrna OP supports “napps” requests in the future.

This comes with two comments :
-	The napps Openid WG has not finalized its documents, thus the “napps” applicatuin type is a draft definition.
-	Mobile device OSs  can provide the “napps” SSO functionalities natively

Openid-specs-mobile-profile mailing list Openid-specs-mobile-profile at lists.openid.net

More information about the Openid-specs-mobile-profile mailing list