# Automatic authentication from many different URIs

**URL:** <https://meta.discourse.org/t/automatic-authentication-from-many-different-uris/45018>\
**Category:** SSO\
**Created:** [May 31, 2016, 3:17am 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:** 4

<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:** [May 31, 2016, 8:24am UTC](https://meta.discourse.org/t/automatic-authentication-from-many-different-uris/45018/4 "2016-05-31T08:24:00Z")

</div>

Thanks Matt; I appreciate the quick response!

I’ll have a look at building out a plugin to handle the token-based authentication – it’s not as robust as building a central authentication server, but it has the benefit of being a whole lot simpler and therefore a whole lot quicker to build and get into production. 🙂

Down the track, we’ll look at a central authentication server; we’ll likely need something like this for other work in the future, so it’s probably not a bad idea to avoid painting ourselves into a corner.

We would resolve username collisions by making the username the email address – if someone owns the same email address at two instances, they’re the same person. (We don’t do email address ownership verification, but for our particular use-case, that’s less of an issue; we’re deployed into schools, and staff and student email addresses tend to all be within the same domain and thus “owned” by the school.)

---

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