How to set up cross-domain login with Memberstack across multiple domains including an odd one via API? Answered

Post author
Ivan Throne

Looking to implement cross-domain login and running into some issues (I can't get it to work at all). However, solving that has taken a bit of a turn and so I'm requesting some expert help here.

Here's what we're trying to accomplish...

We have several sites that will be using Memberstack:

While I understand that login across the first four bullets can be achieved, is it possible to have the odd domain also included using API calls?

Even if it means purchasing another Memberstack project (we'd prefer one dashboard though!).

We do have a developer now who can work with scripts and API calls, so that helps a bit.

This would be a huge deal for us. Can it be done?

ALSO: We need a user-facing ticket system. Any recommendations for nice clean integration with Memberstack?

Comments

9 comments

  • Comment author
    Abdullateef Ademoye

    Ivan Throne You can use cross-domain login using a single memberstack dashboard through all your domains by building a custom server to handle requests between your sites and memberstack

    That is, build an api service (backend), which you can host on AWS, Digitalocean, Heroku so it will serve as a communication layer between Memberstack and Your Website frontends.

    0
  • Comment author
    Ivan Throne

    Abdullateef Ademoye Any tutorials around for that?

    0
  • Comment author
    Abdullateef Ademoye

    Your developer should know more if you explain as I just did

    0
  • Comment author
    Ivan Throne

    Copy, thank you

    0
  • Comment author
    Vladimir Babic

    Hey everyone, quick DNS question.

    We have an app hosted at app.domain.com, and we want it to support cross-domain logins—meaning users logged into our main app should automatically stay logged in on app.domain.com.

    To make this work, we need to update our DNS settings.

    The site is fully operational, with 20k users and 3.5k paying customers, so we’re being very cautious about making changes in Memberstack. Are there any risks we should be aware of if we proceed with the standard 4-step DNS domain setup now?

    0
  • Comment author
    Raquel Lopez

    Hello,

    There shouldn't be any risk, because you won't have to change the main domain, just adding one.

    If you already have the "custom domain" successfully configured, you don't need to change it, because then it will break things.

    Please, keep in mind that for cross domain to work you need to enable cookies and the different domains should share the same root domain.

    I'm attaching the documentation so you can use it as reference

    https://docs.memberstack.com/hc/en-us/articles/18004875142555-Enable-Cross-Domain-Login[…]ga_M18GBY4NJ0*MTc0NTUwOTQ1NC4xOS4wLjE3NDU1MDk0NTQuNjAuMC4w

    0
  • Comment author
    Nihat Avcı

    I have a website built with Webflow. I also have another website built with Next.js, and I want to connect it to Memberstack as well. I want to make it so that when a user visits my Webflow site, logs in, and then clicks a link to go to my Next.js site, they stay logged in without any hassle. Essentially, I want the user management to work smoothly across both sites, as if they are part of the same website. How can I set this up? is this possible?

    0
  • Comment author
    Raquel Lopez

    Yes, you can do it as long as both sites share the same root domain https://docs.memberstack.com/hc/en-us/articles/18004875142555-Enable-Cross-Domain-Login-with-Memberstack

    0
  • Comment author
    Nihat Avcı

    So one root, one subdomain is okay then? Thank you :))

    0

Please sign in to leave a comment.