[openstreetmap/openstreetmap-website] Add MAPS.ME authentication (#1433)

[Ilya Zverev]

> I don't see anything in [theregister article] indicating that an app accessing the OSM API won't be able to use a webview for the the user to authorize a OAuth request on osm.org.

This concerns only the Google authorization. You can log in or sign up to OSM with a Google profile, instead of typing a password.

> The blog post goes on to say how "in-app tabs" are also an improvement for security. Would Google's suggestion be an easier (and possibly more secure) upgrade path for anyone currently doing OAuth in a WebView?

The easiest solution would be not to use these in-app tabs (suppored only on Android 4.1+, while even maps.me supports 4.0.3+), but to use the Google Native SDK. Unfortunately, with OSM that is not an option now. With maps.me authentication it will be.

> >  What matters is mappers answering e-mails, and this is a step in that direction.
>
>Please could you explain how this PR helps? At the moment, I can't see how it adds anything we don't already have in our Google and Facebook integrations.

Our Google and Facebook integrations do not allow seamless login with mobile devices. Users have to retype their passwords — and I don't even know mine. As for the user feedback, this PR will help us better integrate the new profiles into the maps.me mapping experience, and I hope that later OSM would have better notifications API, and maps.me profiles will have these notifications prominently displayed.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/1433#issuecomment-283135778
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20170228/3b3ba67e/attachment-0001.html>