# Authentication Protocol re: App Integration

**URL:** https://meta.discourse.org/t/authentication-protocol-re-app-integration/114788
**Category:** Development
**Created:** [April 11, 2019, 5:24pm UTC](https://meta.discourse.org/t/authentication-protocol-re-app-integration/114788 "2019-04-11T17:24:07Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![hosna](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hosna/32/99969_2.png) [@hosna](https://meta.discourse.org/u/hosna)
#### Post date: [April 11, 2019, 6:48pm UTC](https://meta.discourse.org/t/authentication-protocol-re-app-integration/114788/2 "2019-04-11T18:48:11Z")

</div>

There is a new way of authentication. However the documentation is yet to be released.

> [@Delegated authentication for Discourse Mobile app](https://meta.discourse.org/t/delegated-authentication-for-discourse-mobile-app/110414):
>
> 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 cookies”](https://blog.branch.io/ios-11-safari-view-controller-cookie-passthrough-and-the-future-of-mobile-web/), this meant that you had to log in to the application web sites AGAIN after already being logged in, in Safari. To add additional layers of pain crying_cat_face , cookie management in Safari Vi…

---

_[View the full topic](https://meta.discourse.org/t/authentication-protocol-re-app-integration/114788)._