# Accessing one discourse via two different SSO backends

**URL:** <https://meta.discourse.org/t/accessing-one-discourse-via-two-different-sso-backends/118591>\
**Category:** SSO\
**Created:** [24.Май.2019 07:16:59 UTC](https://meta.discourse.org/t/accessing-one-discourse-via-two-different-sso-backends/118591 "2019-05-24T07:16:59Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![theopen-institute](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/theopen-institute/32/141988_2.png) [@theopen-institute](https://meta.discourse.org/u/theopen-institute)\
**Post date:** [24.Май.2019 07:16:59 UTC](https://meta.discourse.org/t/accessing-one-discourse-via-two-different-sso-backends/118591/1 "2019-05-24T07:16:59Z")

</div>

My organization has been slowly rolling out discourse for a range of communication purposes, and everybody absolutely loves it. I’ve seen few projects anywhere that manage to combine big picture thinking and attention to detail so well. Thank you, to everyone who has built this wonderful thing.

A practical question: our discourse community is composed from two distinct groups, one of which is based in our Moodle learning management system and the other of which is based in our internal admin system. We’d like to implement single sign on functionality for both groups, but we’re unsure about the best way to proceed.

If we pointed two different subdomains at the same discourse, would it be possible to write a plugin that would route logins to one or the other SSO link based on the subdomain being accessed? Or, is there another, better way we should be thinking about this?

---

_[View the full topic](https://meta.discourse.org/t/accessing-one-discourse-via-two-different-sso-backends/118591)._
