Both are on a different project within Wappler - but both point to the same external managed DB (AWS RDS).
Is it possible to log a user in on www.maindomain.com and redirect them to the app without any security session cookie issues etc. ?
If so, what would be the advised way to do this?
Will simply logging a user in with the same DB using the security provider and security login actions in the SC create a session that will work across both?
Little friendly bump - would really like to know if this is even possible? Ran some tests last night and couldn’t get it to work, wondering if I can set a session or something that would work? Any pointers to documents/guidance would be appreciate - need to ideally figure this out this week!
@Teodor would you mind providing some guidance here please? I need to make some logic decisions based on if this is or is not possible.
I want someone to be able to login on project 1 (main domain) and for the security session/login to persist as I redirect them to the app - project 2 (sub-domain).
It wasn’t working no, unfortunately. I’ll triple check everything. Do I need to set the Security provider with the same Secret Key on both projects/domains?
Hi, i did it last year. Two different wappler projects, one on domain.com and one on sub.domain.com and it worked… Just copy paste the data from first security provider
@Teodor looking at some of the session data in the console, it looks like it might be - but how would I access a users session information purely using App Connect, and no SC actions? (I want to set a condition if a user is logged in, on another domain).
Ok, thanks Teodor. Very new to this part - trying to figure out how to set conditions when a user is already logged in on another domain, (cross domain).
use conditions on app.mydomain.com based on their logged in session_id. E.g. instead of a login form (if logged in) - show a different form, instead - and even show that they are logged in in the nav header.
