Hello everyone,
We have a WordPress customization scenario that is breaking Discourse plugin functionality.
Scenario
- My site is WordPress site. Let’s say abc.com
- I have Discourse WordPress plugin installed and it works just fine to login to Discourse after I have logged into WordPress. I have to just click on the login button on Discourse and the user is auto logged in.
- The community is hosted on community.abc.com
- Now I have created a domain alias for my site as a white label solution for one of my client. Let’s say the new domain is abc.client.com
- This new domain allows the client to access the site in a completely white label manner. We don’t want then to access any content via the abc.com domain.
- Now, when the user from the client side logs in to abc.client.com (wordpress white label site), and then clicks on the community link, they are directed to community.abc.com.
- When the user clicks on login button on the community they are not auto logged in to the discourse site, and instead the page is redirected to abc.com/login/?redirect_to=%2Flogin%3Fsso…
- This redirection is not desirable as user would have to login to abc.com and then only access community.abc.com
- Question – is there a way to login to the discourse community after the user logs in to abc.client.com ?
This might be an issue related to the change in webhook as the domain alias used. Is there a workaround to make it happen? Does the user have to logged into abc.com to be logged in to the discourse community? Can there be two domains that login to the same Discourse community?
Appreciate your support.