No hurry. Thanks for all the work you put into this.
I’ll try to reduce the scope.
I am using Discourse as the SSO provider to WordPress. Currently, I have this set at the Network level in the plugin settings. This appears to be functioning as expected.
It seems that my current setup reflects the intended behavior. That is based on this note in the plugin options of the subsites:
You are using the WP Discourse plugin in a subsite of a multisite installation. The plugin’s API credentials are being managed through the installation’s main site. If you have difficulty connecting to the Discourse forum. Please contact the network administrator.
If that is correct, then my first observation is that there doesn’t seem to be a way to change the Publishing Username on the subsites. In my scenario, each subsite is owned by a separate Discourse user who is a human who wants to be associated with their blog posts. Ideally, each post they make from their subsite would be published to Discourse as their own username.
If I disable the multisite option in Network, the subsite Publishing Username reverts to the desired subsite behavior. However, the tab to put WP in SSO Client mode disappears. Does using Discourse as SSO Provider only work if Enable Multisite Configuration is selected in the Network settings? The SSO settings are still present in the Network UI when it isn’t selected.
In other words
As I alluded to initially, part of my confusion relates to our earlier discussion which included discussion of filters to exempt some subsites from the multisite config.
Is it possible to get these three behaviors simultaneously:
- Each subsite publishing to Discourse as Username of the subsite owner
- Discourse as SSO Provider for all WP subsites
Advanced. One subsite publishing to an entirely different Discourse install