# Delegated authentication for Discourse Mobile app

**URL:** <https://meta.discourse.org/t/delegated-authentication-for-discourse-mobile-app/110414>\
**Category:** Development\
**Created:** [01.Март.2019 05:12:44 UTC](https://meta.discourse.org/t/delegated-authentication-for-discourse-mobile-app/110414 "2019-03-01T05:12:44Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [04.Март.2019 11:54:10 UTC](https://meta.discourse.org/t/delegated-authentication-for-discourse-mobile-app/110414/4 "2019-03-04T11:54:10Z")

</div>

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 this terminology? In core we [already have the concept of “tokens”](https://github.com/discourse/discourse/blob/master/app/controllers/session_controller.rb#L290-L304) - these are used for the “login by email” system. I think it makes sense to build on this, rather than making a whole new redis-backed system.

As an aside, is there a reason why we have a discourse-specific process for “User API Keys”, rather than following some open specification like OAuth/OIDC?

---

_[View the full topic](https://meta.discourse.org/t/delegated-authentication-for-discourse-mobile-app/110414)._
