I had a similar situation in a instance, and what solved for me was having both sites under the same Identity Provider using DiscourseConnect - Official Single-Sign-On for Discourse (sso).
5 Likes
I had a similar situation in a instance, and what solved for me was having both sites under the same Identity Provider using DiscourseConnect - Official Single-Sign-On for Discourse (sso).