You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question about if it's possible with Ory Network to support sign up and log in for users across multiple different domains.
For example, I have four separate domains I would like one Ory Network instance to support:
shop.company.com
company.com
alpha.io
beta.live
Assuming my Ory Network's custom domain is auth.company.com, I believe shop.company.com and company.com shouldn't have an issue authenticating and receiving the Ory session cookies to then call the Ory /sessions/whoami endpoint from the original app (shop.company.com or company.com) and show the user's logged in view.
However, I'm unclear as to whether alpha.io and beta.live can also receive cookies to perform the same /sessions/whoami call to auth.company.com.
Is it possible to allow those particular URLs to somehow receive Ory session cookies even though they have different domains?
My main concern right now is that once a user has registered within one of these properties, they can sign in later through any of the other properties (or be automatically shown the logged in view based on an existing Ory session token in the browser's cookies).
Is this something OAuth2 might be able to assist with? I'm reading up on OAuth2 now, but I'm still very new to it.
Thanks for any advice you can provide on helping me to understand what Ory can support!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I have a question about if it's possible with Ory Network to support sign up and log in for users across multiple different domains.
For example, I have four separate domains I would like one Ory Network instance to support:
Assuming my Ory Network's custom domain is auth.company.com, I believe shop.company.com and company.com shouldn't have an issue authenticating and receiving the Ory session cookies to then call the Ory
/sessions/whoami
endpoint from the original app (shop.company.com or company.com) and show the user's logged in view.However, I'm unclear as to whether alpha.io and beta.live can also receive cookies to perform the same
/sessions/whoami
call to auth.company.com.Is it possible to allow those particular URLs to somehow receive Ory session cookies even though they have different domains?
My main concern right now is that once a user has registered within one of these properties, they can sign in later through any of the other properties (or be automatically shown the logged in view based on an existing Ory session token in the browser's cookies).
Is this something OAuth2 might be able to assist with? I'm reading up on OAuth2 now, but I'm still very new to it.
Thanks for any advice you can provide on helping me to understand what Ory can support!
Beta Was this translation helpful? Give feedback.
All reactions