You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Passport's authentication middleware, which provides an authenticated user object on a request (Passport Middleware Documentation). I'm struggling to access this user object in services.
A potential workaround is to do a double lookup in the service based on the cookie, but I'd prefer not to. It seems counterintuitive for a library to obscure objects, especially when there's an ecosystem contributing to them. This makes integration challenging.
The text was updated successfully, but these errors were encountered:
Thanks for raising this, @akosyakov. We'll address this through augmentation of the HandlerContext, see #527 and the comment collecting use cases in different frameworks.
I'm using Passport's authentication middleware, which provides an authenticated user object on a request (Passport Middleware Documentation). I'm struggling to access this user object in services.
A potential workaround is to do a double lookup in the service based on the cookie, but I'd prefer not to. It seems counterintuitive for a library to obscure objects, especially when there's an ecosystem contributing to them. This makes integration challenging.
The text was updated successfully, but these errors were encountered: