Session variables lost on auth-callback when deployed to production
-
I've been using this solution to test the fusion auth apis for multi tenancy.
The example works well for a single application but when we try to replace the config values with injected variables into the session from the login service, when we intercept the request in oauth-callback the session variables are not available when deployed to a production server under Https.
If i run this locally using http://localhost:4200 for the angular app and http://localhost:3000 for the server, the session variables persist from login to oauth-callback.
I read some articles about adding withCredentials = true which i have done but that doesn't seem to solve the problem.
Has anyone else had this issue and if so how did you resolve it?
Or alternatively, does anyone have a github repo that implements multi tenancy using Fusion Auth?
-
I'm not sure what is going on, but my guess is that the cookies are shared locally (cookies are shared across ports), which is why things are working.
If you are trying to pass information from when someone logs in to after they are logged in, through the oauth flow, you should look at the
state
parameter. There's some information on doing that here: https://fusionauth.io/community/forum/topic/165/taking-a-user-directly-to-the-registration-page?_=1610507951768 but I'm not sure how it integrates with whatever library you are using. I'd consult the docs for that lib.