Originally when we built the mobile app Apple offered seamless embedding of Safari in mobile apps. All was good, you could log in to Safari, and magically with one click have the application authenticated. However, fast forward a few years and Apple released iOS 11. Sadly, this broke “shared cooki…

Does this also solve my problem? [이미지] Passwordless signin via link generated by api Feature Is it possible? I didn’t see this feature in api. I saw that passwordless signin via email link is already planned. Maybe this feature would also be possible? Use-ca…

This sounds like a great improvement - getting set up with the app is a pretty frustrating process right now! [이미지] sam: one time password… stored in redis I had to read through this spec twice before I realised you weren’t talking about two-factor “one time passwords”. Is there a reason for…

[이미지] david: I had to read through this spec twice before I realised you weren’t talking about two-factor “one time passwords”. Is there a reason for this terminology? Yeah we can use the existing token infrastructure here, however I want to make sure that We ship the token encrypted using …

I have started working on this and have a few things to verify regarding the advanced flow: I don’t think we need to send the public key on every request in SafariViewController. The app currently sends discourse_app=1 which flags the session as coming from a mobile app. If user is logged in, disc…

[이미지] pmusaraj: I don’t think we need to send the public key on every request in SafariViewController. The app currently sends discourse_app=1 which flags the session as coming from a mobile app. If user is logged in, discourse_app=1 can be stripped by Ember and the user can continue using the s…

[이미지] sam: This can be particularly confusing if https://meta.discourse.com?discourse_app=1 is visited from a random browser on the phone Yes, I see the redirect issue and the confusion it would introduce. Signing a piece of transient data makes sense, I will look into that. Re: ASWebAuthent…

Re ASWebAuth the only difference is that you stay in the app vs get bounced to Safari? (And pay the price of an extra pop up for not being bounced)

Yes, you stay in the app, and you need to confirm the extra popup. Unlike in Safari, you don’t see an address bar, only a “Cancel” button in the top left corner.

As this feature is in the new release, can I ask how actually it works?

Please wait a few more weeks, while we test the new version of the app

Delegated authentication for Discourse Mobile app

개발

hosna (hosna) 4월 27, 2019, 5:45오전 13

Now that the ios app is released, can we have some documentations about this feature?

글		댓글	조회수
Authentication Protocol re: App Integration Development	16	2560	3월 31, 2020
New iOS mobile app beta available for testing Development dev-news	54	5034	2월 25, 2025
Passwordless signin via link generated by api Feature	15	2225	3월 5, 2019
Webauthn support Feature rfc	46	6918	11월 3, 2020
Sign in with Apple Feature	61	11316	11월 27, 2020

Delegated authentication for Discourse Mobile app

Related topics