Explanation of the scheme (this is the maximum option that I can imagine):
2 or more Discourse multisite installations. Discourse 0 is a common SSO provider for other Discourse (in the same installation or another). It is also a SSO provider for the network “WP Multisite host 2” and individual network sites “WP Multisite host 1”. Some single WP or / and some Ghost websites.
Arrows in the diagram denote SSO
Is it possible with standard plugins? Any problems?
Discourse 0 in this scheme is essentially only an SSO provider. Is it possible to turn off the forum in this situation and leave only a few custom pages (for example, with a description of websites / forums to which authorization is given) and the login / registration form?
Or for these purposes it is better to use a stand alone special solution (which one?)
Nah, that would work. My only question is why you would have different forums if they’re all accessible by the same user base anyway?
What do you mean?
As far as I know, discourse multisite is just a common file base. DB and, accordingly, their users are different.
This is not the same as Wordpress Multiste where users are in the same database on all sites on the network.
Perhaps I am mistaken.
There will be different databases yes, but will the users in them be different if you delegate access control to a central SSO provider? At most, some users will not exist on some forums… but I don’t see a big difference between this and one forum with multiple categories.
So I’m just curious about your use case for this.
Of course, for my purposes it would be more convenient if all the Discourse Multisite forums were linked by a common user base. But it is not.
I have to choose and install a central SSO provider myself. About this and my whole question.
This is my target
Why not one forum with subcategories:
Why one user base
But… if you have multiple forums about completely different subjects, will they share (a large part of) the same users at all? If the answer is no, then the reasons for one userbase will only have a minimal impact.
No, I said related subjects. For example: cats owners website, dogs owners website, home pets forum, Livestock Forum, online shop with pet toys/food, veterinary directory, etc
Perhaps any 2 topics will not be related to each other, but they can be linked through a third. This is how networks are built. All this because of possible synergy. It may not be, but to miss the opportunity is stupid, if it can be done.
My first scheme is not fully correct. This is more correct case:
violet arrows - SSO
red arrows - comments
Discourse 0 needed only for SSO, not for comments or discussions.
@unicom Curious if you ever implemented this? I agree on the possible synergies you could drive…
不，这只是我能想到的最复杂的电路。我只是在摸索 Discourse 的极限。在现实生活中，我还没有遇到过如此困难的、涉及多个 discourse 的任务，我现在认为为 SSO 任务分配一个单独的 discourse 是过度设计。如果你得出了这个结论，那么你就走错路了。
现在我坚持“从一般到具体”的思路。也就是说，继续我上面给出的例子：你首先打开一个专门讨论所有宠物、它们的治疗和食物的通用论坛，当它发展壮大时，你会发现有必要将几个大类分离到一个单独的论坛（猫主人和狗主人，因为这是最大的两个类别，它们之间相处不好，而且它们对阅读彼此的问题并不太感兴趣）。那时你就可以使用你的原始论坛作为这两个新论坛的 SSO 提供商。它们将协同工作，但不会因为过于接近而受到影响。
我看到的第二个用例是创建独立的语言论坛，其中中央论坛是主要语言，再加上几个其他语言的论坛，通过 SSO 连接到该主题。但这应该在所有使用的语言都得到同等支持的情况下进行。而且你也许也应该从一个论坛开始，为语言设置单独的类别，当它发展壮大，沟通变得不方便时，再分成不同的论坛。
这里的关键应该是所有论坛之间的用户账户自动同步，以及在进入其中一个论坛/网站时自动登录到所有论坛/网站。
