# Native SSO with Azure AD

**URL:** https://meta.discourse.org/t/native-sso-with-azure-ad/105509
**Category:** SSO
**Created:** [January 2, 2019, 7:46pm UTC](https://meta.discourse.org/t/native-sso-with-azure-ad/105509 "2019-01-02T19:46:05Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![andy.czerwonka](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andy.czerwonka/32/122379_2.png) [@andy.czerwonka](https://meta.discourse.org/u/andy.czerwonka)
#### Post date: [January 2, 2019, 7:46pm UTC](https://meta.discourse.org/t/native-sso-with-azure-ad/105509/1 "2019-01-02T19:46:05Z")

</div>

Can we use the native SSO capability (no external plugins) as use Azure AD as the authentication provider? The workflow we’re looking for is similar to that of logging into any Office 365 app, i.e. it would simply redirect to the Microsoft authentication page as part of the sign-in when the session is not authenticated.

---

<div class="post-metadata">

### Author: ![andy.czerwonka](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andy.czerwonka/32/122379_2.png) [@andy.czerwonka](https://meta.discourse.org/u/andy.czerwonka)
#### Post date: [January 2, 2019, 7:48pm UTC](https://meta.discourse.org/t/native-sso-with-azure-ad/105509/2 "2019-01-02T19:48:15Z")

</div>

If not, I think the [Discourse OpenID Connect (OIDC)](https://meta.discourse.org/t/openid-connect-authentication-plugin/103632) could work, but it would be nice to have all the “sso overrides” features, e.g. the name and avatar from their account.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [January 2, 2019, 9:29pm UTC](https://meta.discourse.org/t/native-sso-with-azure-ad/105509/3 "2019-01-02T21:29:56Z")

</div>

You will need to write a small web service that translates between the Azure AD protocol and the [Discourse SSO](https://meta.discourse.org/t/13045?silent=true) protocol.

That is doable and it doesn’t need to be a Discourse plugin, so you can use whatever technology you want and host it wherever works best for you.

---

<div class="post-metadata">

### Author: ![consideRatio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/consideratio/32/126623_2.png) [@consideRatio](https://meta.discourse.org/u/consideRatio)
#### Post date: [March 26, 2019, 7:58am UTC](https://meta.discourse.org/t/native-sso-with-azure-ad/105509/4 "2019-03-26T07:58:40Z")

</div>

I built on top of the work of others, and made [GitHub - consideRatio/discourse-sso-oidc-bridge: Discourse SSO OIDC Bridge - A Python PyPI package · GitHub](http://github.com/consideratio/discourse-sso-oidc-bridge). So, if you have a provider that you want to use OIDC with, but also [discourse SSO](https://meta.discourse.org/t/13045?silent=true), then this is a solution.

( I have some trouble with using my IPhone without any interruptions now though, but it may be unrelated to the bridge. I run into a redirect loop between discourse and the discourse-sso-oidc-bridge when returning from my OIDC provider, but only on IPhones, and everything works if i reload the page of discourse. See: [SSO redirect loop with Lax cookies, but only for my IPhone?!](https://meta.discourse.org/t/sso-redirect-loop-with-lax-cookies-but-only-for-my-iphone/112579) )
