[Wishlist] Eliminating double login requirement for Memberstack SSO integrations like Circle and custom domains

Duncan from Memberstack asked January 24, 2023 14:14

Implemented

1) The problem → Members sign up or login on my domain and they have to log in again to access my SSO integrations (Circle, Custom, etc.)

2) Why is this important → User experience is important to my brand and to me. I want there to be as little friction and opportunity for confusion as possible.

3) What's your plan B → Require customers to log in twice... or build something custom outside of Webflow.

4) Possible solutions we could build for you → Allow customers to automatically be logged in when they visit my various sites and various domains.

3 comments

Josh Lopez Official comment September 24, 2026 01:21

In Authentication → Custom SSO you can now set a login page URL for each SSO app, so members sign in on your own site. Members who are already logged in there aren't asked to log in again, and you can skip the consent screen.
Duncan from Memberstack OP January 24, 2023 14:15

From the team

We attempted to remove the 2nd login but could not because of the Open ID Connect protocol.

Essentially the issue is that members first log into your website on your domain, and then the circle SSO flow occurs on our domain. We can’t carry over the authorization between domains…

To be 100% transparent - There are possible solutions to this that we’ll explore at some point in the future (such as allowing you to add a custom domain to memberstack, etc.), but no solutions are scheduled for development at this time.

0
Yoav Schwartz November 26, 2024 18:04
Hi, hoping there's been progress here in the past 2 years.

I've got everything set up so that Circle, my custom app and Memberstack all share the same root domain.

I'm connecting memberstack with Circle.so in the following way:

When someone signs up on signup.mydomain.com (react/nextjs), on success, they are redirected to circle.mydomain.com/checkout/sub?autologin=true, which redirects them to auth.mydomain.com (hosted by memberstack)...

at minimum, my understanding is they should already be signed in on auth.mydomain.com because i have set on signup.mydomain.com:
```
useCookies: true, setCookieOnRootDomain: true
```
However, they still need to sign in on auth.mydomain.com, (which creates their account in circle) and then shows them a "authorize" modal (which doesn't mean anything to the user as they don't understand they are connecting 2 systems), and only then do they get sent to circle.mydomain.com/checkout/sub where they are signed in to their new account.

this will undoubtably lose many people in the flow.

Thanks for your help
2

Please sign in to leave a comment.