[Shipped] Use Memberstack on multiple sub-domains Completed
1) The problem → I can use Memberstack on multiple websites / domains, but I don't want members to have to log in every time they switch websites. A portion of my content lives on another website/subdomain/CMS.
2) Why is this important → My CMS isn't on my main marketing site (where people log in) and I really don't want to give up my CMS. It's core to my value prop.
3) What's your plan B → Leave half of my content "unlocked" or move all of my content into a single domain.
4) Possible solutions we could build for you → I love love it if a session carried over between domains. So, a member could log in on mywebsite.com and then access content as a logged in member on app.mywebsite.com. Both websites would have the same Memberstack script installed.
Comments
13 comments
Finished 🎉 🎉
This feature has been released and is fully documented below. If you have any questions feel free to leave a comment here or in the official article.
Enable Cross-Domain Login with Memberstack
This would be the perfect result for us. We use Webflow as our customer-facing site. We also use multiple other servers to provide additional services. To link it all through Memberstack and Webflow would be perfect.
Thanks Duncan. My use case is that I use webflow as the frontend and have an application running on the subdomain which needs to be gated. Would prefer not requiring double logins. And would also prefer not to run the application in an iframe on webflow since that isn't very secure (someone could just copy/paste the application url for example). Am open to suggestions
Did I sum this up well?
Yes exactly!! I’m not sure if this is the same or different but just multiple sites in general would be awesome. E.g. one membership gets access to multiple sites. That’d make bundling really easy.
Yeah this is huge. We don't use any of our app facing Webflow projects on the same projects that are used to advertise and sign up. The core reason for this is both reducing the restrictions of Webflow CMS items, as well as creating a more separated environment (particularly when we're using custom code).
At this time, I don't really know a way around this which means we can't really use MS.
Ollie Law I'm super bummed to hear that and I can imagine it's a frustrating realization.
I wish we could enable this ASAP too. Unfortunately, we're fighting browser security protocols and hitting blockers. We get a bit further each time before pushing it further down the roadmap. We'll keep working on it and hopefully get a solution out in the not too distant future 🤞
Also facing same problem. We're looking to launch our content brand (CMS) on domain.com, but have our Node.js app on app.domain.com.
Ideally we can keep the logged-in state persisting across the subdomain and the domain.
Chuck Lapointe I'm excited to share that Tyler Bell got a prototype up and running very recently. The feature doesn't have a scheduled launch date, but it's in active development. I'll share an update here once it becomes available.
Hi Duncan,
Is this available?
I am looking to do this today as the paid part of my content is hosted on a different URL and I am unable to bring that into Webflow.
Is there another workaround that we could implement for now?
Max Milstein It's not available yet, but we're getting closer. We recently made some new DNS feature available that set the foundation for this feature.
Very excited to see a stable release of this feature!
I really want this too please. to be able to restrict access to members only for app.mywebsite.com
Please sign in to leave a comment.