Nativescript: Q: RFC#8252 OAuth2 for Native Apps support

[Peperud]

I realize that this question might not belong here. If that is the case, please point me to the right place.

Last year IETF officially came out with a best practices recommendation on implementing OAuth 2.0 for native apps.
The gist of it is that the apps should not drive a WebView and instead must use the system browser.
There are AppAuth-iOS and AppAuth-Android open source projects.
There's also AppAuthJS, however it seems to be Node/Desktop bound.

Are there any plans for NativeScript - AppAuth integration?

Generally speaking - solid OAuth2/OpenIdConnect support would be quite welcome in corporate environments.

[NickIliev]

@Peperud there is this plugin which uses OAuth2.

You can post feature related questions in the community channels as well - use the NativeScript forum, SO or the community NativeScript slack channel.

[Peperud]

@NickIliev that plugin does drive a web view (I'm guessing that's why it doesn't work with Google, since Google no longer allows it) and have a rather narrow list of supported providers.
IMO the right solution should work with any provider that supports OAuth2/OpenIdConnect specs.
More like what this React-Native project is aiming for.

[NickIliev]

@Peperud logging this one as a feature request and perhaps the community will come up with a plugin that enables AppAuth. As NativeScript is an open source project anyone interested can become a contributor and implement this as a plugin.

[NickIliev]

@Peperud as of this moment you can use NativeScript Sidekick to create kidney auth template and choose from different authentication providers including Auth2 with Kinvey.

You can install NativeScript Sidekick, and create new. Enterprise Auth template to test the Auth2 functionality provided by Kinvey.

Closing the issue as resolved as kinvey-nativescript-sdk plugin is proving this functionality

[Peperud]

@NickIliev thanks, I saw that. Doesn't work for me because of this bug, but it sounds good.

[adityamenonsrijan]

I'm sorry - I fail to understand how this can be closed as "resolved" - when the only way to provide the feature OP is asking for, which is based on Open Standards, in this Open Source project - is with a proprietary backend provider? Could you please clarify?

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.