Discourse-saml is not multisite compatible

Contribute Feature
6

Yes this is what I just realized. It’s very unfortunate. :frowning:

So actually, the plugin’s non-compatibility means that:

  1. it will work on the first site of a multisite (or the one for which it’s configured via DISCOURSE_HOSTNAME)
  2. the button will appear on all other instances’ login UI
  3. but those buttons will fail without a clear solution.

Since there’s no dedicated topic in Customization > Plugin for discourse-saml, I’d suggest to create one and mention this caveat in the first post. I’m pretty sure some consolidation can be made from the 50+ topics mentioning SAML. Had I known this before I would have setup my services differently.

(BTW, the original CSP error is most probably due to the fact the iframe tries to load the original site instead of the current one.)

Hide SAML Button on multisite

This is a quick fix for people who activated the SAML plugin on multisite. :slight_smile:

  1. Go to Admin > Themes and “install new”
  2. Create new component (with name: “Hide SAML Button”)
  3. Add CSS:
    #login-buttons .btn.btn-social.saml {
    display: none; /* plugin incompatible with multisite */
}
  4. Apply component to all themes.

Now the SAML button (which does not work on this instance) remains out of view.