0
I would like to know how I can store user information individually without using Constants and Session to be accessed by my data access project?
It used constants but the application was transformed into Saas and constants ended up giving conflict if there was more than one user logged in at the same time.
The goal is to store a dynamic string Connection per user to be used by the data access layer.
if you are not going to use Session you need to use a database, and for example a token that will serve as a user session id
– Ricardo Pontual
But I need to access this string Connection to know which database to connect to, not use a database
– Victor Laio
At least you need a "Energy" bank to save sessions, then you can use that to decide what to do, like open a specific connection. It is a bit confusing, without more details becomes difficult to help, the fact is: to keep a logged-in user session you will need to save it in one place, and it could be a "session database"
– Ricardo Pontual
I understood, and there would be no other way to do that?
– Victor Laio
There are several approaches, but to be able to give an answer you need to present a [MCVE]
– Leandro Angelo