Android Application Question

[Rainer Hoerbe]

> Am 04.01.2017 um 16:30 schrieb Cantor, Scott <cantor.2 at osu.edu>:
> 
> On 1/4/17, 10:22 AM, "users on behalf of Marc Boorshtein" <users-bounces at shibboleth.net on behalf of mboorshtein at gmail.com> wrote:
> 
>> getting a bit off topic but its funny because people created openid connect because they didn't like SAML/XML (especially
>> in mobile apps) and now that google is pushing everyone to using the system browser (which was really always the *best*
>> way to do it) the mechanism for SSO is irrelevant to the client app.
> 
> Yes. I thought about noting that specifically in my response with a snarky comment about how "well suited" OAuth is to mobile, but decided to wait until the second week of January to start being snarky about it.


The NAPPS (OpenID Native Apps SSO) WG is working on a standardized interface to a native token agent. This will move the responsibility for the native app to IDP interface to another place. In that context it is worthwhile to mention that there is an alternative emerging between system and embedded browsers: the web controller:

https://developer.pingidentity.com/en/resources/napps-native-app-sso.html <https://developer.pingidentity.com/en/resources/napps-native-app-sso.html>

Does not apply to QT5 applications, but might be useful in other settings.

- Rainer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170104/a2a8d57c/attachment.html>