IDEA: Centralized userId

Yes, I think what I am proposing would be compatible with any authentication module, with little or no alteration. The point isn’t so much to hook the *services* performed by authentication and authorization (leave those to the libraries) but to curate the *results*. What I’m interested most specifically is a way of identifier “current user” independent of the module or library used to determine that user, so (I think I might have said this already) for example I could populated a “created by” field on a completely unrelated module.

I’ve been thinking on how I would do this if I did it myself (and might send over a PR as an example), but I’ve been thinking a simple set/get method to the session library along with predefined events. Then a module could call session()->user($loggedInUser) or $event->trigger(‘login’, $loggedInUser) and the framework would handle everything for other modules.