Set up Discourse as a SSO provider for GitLab EE
Intermittent downtime 2019-01-13 due to attempts to set up SSO
I spontaneously started trying to set up SSO for our Discourse and GitLab EE installations today, which caused intermittent downtime. In the past, there were at least eight different web applications for Chakra - all with separate accounts. Now, there’s only Discourse, GitLab EE, and the CCR. Even with a variety of OAuth2 providers supported, such as Bitbucket, Facebook, GitHub, GitLab, Google, Instagram, Twitter, and so on, it would be nice to have a single sign-on (SSO) solution for our Discourse and GitLab EE installations. One of the two (preferably Discourse, the way I look at it) would act as the SSO provider, to which the other sends any authentication requests. In short, one account for the both of them.
The result after today is that you can now create a new account, or connect an existing one, for Discourse, in GitLab EE. I recommend not doing it, because I’ll most likely give this another shot later, and try to get it done my way.
~ totte, this post
I think JWT might do the trick. Try that next.