# Automatic authentication from many different URIs

**URL:** <https://meta.discourse.org/t/automatic-authentication-from-many-different-uris/45018>\
**Category:** SSO\
**Created:** [31. Mai 2016 um 03:17 UTC](https://meta.discourse.org/t/automatic-authentication-from-many-different-uris/45018 "2016-05-31T03:17:41Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![barryvan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barryvan/32/82635_2.png) [@barryvan](https://meta.discourse.org/u/barryvan)\
**Post date:** [31. Mai 2016 um 08:26 UTC](https://meta.discourse.org/t/automatic-authentication-from-many-different-uris/45018/5 "2016-05-31T08:26:39Z")

</div>

> [@fefrei](#):
>
> A similar approach is to develop a small web service that acts as a SSO endpoint for Discourse, and handles authentication as you explained. I’d prefer SSO if your are certain that only users of your app should use Discourse, and prefer oauth2 if you also want to support different ways to log in (e.g. for potential customers).

That’s not a bad idea, Felix. I’m not sure if I necessarily want to close the door on allowing potential customers in to the forum, though – it could be a really valuable part of pre-sales and pre-implementation. So for now I’ll look to build the token-based authenticator such that it’s seamless when you’re coming from the software itself, but still allow other people to login directly.

---

_[View the full topic](https://meta.discourse.org/t/automatic-authentication-from-many-different-uris/45018)._
