Remah
3. Februar 2019 um 21:03
3
I’m not sure why you haven’t got a response here. Unless others are waiting for you to do some simple searches on this site. Anyway, I hope this helps as I’m no expert on SSO.
SSO or SAML connection will be by setting an SSO/target URL at Discourse.
Have you read these topics on Discourse and off-site SSO?
DiscourseConnect is a core Discourse feature that allows you to configure “Single Sign-On (SSO)” to completely outsource all user registration and login from Discourse to another site. Offered to our pro, business and enterprise hosting customers .
Discourse SSO ’ is now ‘DiscourseConnect ’. If you are running an old version of Discourse, the settings below will be named sso_... rather than discourse_connect_...
As the administrator of a forum that is using DiscourseConnect , you may occasionally get reports from users that when they attempt to login to the forum, they are greeted by an error message. For example: “There is a problem with your account. Please contact the site’s administrator.”
[20%20AM]
discourse connect logging
To debug the issue, the first thing you need to do is to enable the ‘verbose discourse connect logging’ Site Setting on Discourse. If this setting was previou…
Did you find the SAML plug-in ?https://meta.discourse.org/t/adding-saml-sso-as-an-option-but-not-enforced/47035?u=remah
And here’s a comment about preferring SAML over CAS. Interestingly enough, by the author of this software to help with CAS to Discourse:https://meta.discourse.org/t/cas-auth-via-the-sso-api/23381/9?u=remah
Much like the comment above. Note that has useful explanations unrelated to Ruby on Rails:
2 „Gefällt mir“