# SSO: Support multiple "sso url"s

**URL:** https://meta.discourse.org/t/sso-support-multiple-sso-url-s/61758
**Category:** SSO
**Tags:** pr-welcome
**Created:** [4월 28, 2017, 1:34오전 UTC](https://meta.discourse.org/t/sso-support-multiple-sso-url-s/61758 "2017-04-28T01:34:22Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![sascha](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sascha/32/71383_2.png) [@sascha](https://meta.discourse.org/u/sascha)
#### Post date: [4월 28, 2017, 1:34오전 UTC](https://meta.discourse.org/t/sso-support-multiple-sso-url-s/61758/1 "2017-04-28T01:34:22Z")

</div>

We want to use discourse in an unusual scenario where we have 400+ different IdP instances with one central discourse instance as the SP. We initiate SSO from these 400+ portal pages by redirecting to /session/sso, which will redirect to the one configured “sso url”. It would be nice if we could specify the IdP URL in this request, possibly with a whitelist in Discourse.

We currently work around this by querying the /session/sso endpoint server side, extract the Location header of the redirect, and perform the redirect manually.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5월 1, 2017, 1:50오후 UTC](https://meta.discourse.org/t/sso-support-multiple-sso-url-s/61758/2 "2017-05-01T13:50:21Z")

</div>

I am not against adding flexibility here provided the default remains as is today, if you create a carefully tested PR I would consider merging it.

---

<div class="post-metadata">

### Author: ![sascha](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sascha/32/71383_2.png) [@sascha](https://meta.discourse.org/u/sascha)
#### Post date: [5월 4, 2017, 2:07오전 UTC](https://meta.discourse.org/t/sso-support-multiple-sso-url-s/61758/3 "2017-05-04T02:07:17Z")

</div>

Hi Sam,

thank you very much for your response. Unfortunately my ruby skills are like non-existent and I don’t think I’ll be able to create a PR any time soon for this feature request.

Regards,  
Sascha
