Apperantly the above doesn't so i'm looking for a way access the current user. the reason why is because I need to work with multiple schema's in progress and need to set those on the model.
It’s very bad to use session or auth in your constructor as no request has happened yet and session and auth are INHERENTLY tied to an HTTP request. You should receive this request in an actual controller method which you can call multiple times with multiple different requests. By forcing your controller to resolve session or auth information in the constructor you are now forcing your entire controller to ignore the actual incoming request which can cause significant problems when testing, etc.
There's not really enough info here to demonstrate your problem. I've built fully multi-tenant apps without ever needing to touch a constructor, so it is possible. It all depends on how you architect your application.
We are handling sensitive data so we want to separate every account that is active. the idea is to have separate schema's, 1 per account. the public schema contains accounts and users. we don't have things like subdomains etc. all url's are the same.
I need account information as early as possible but have no idea what the best is to achieve that!.