Update an existing entity in verifier about authentication-oauth2 HOT 7 CLOSED

@skinnyworm Did you find a solution for this? I am working on the same flow, but don't see a place to add in req.user

from authentication-oauth2.

@jasondonnette @skinnyworm if the user already exists in the system and they authenticate again, it will attempt to update the user. We recently made an update so that it performs a patch to the user service. #20

If you are looking to consolidate social profiles, (ie. they are authenticated but then want to "connect" their social account) then yes they'd have to be logged in first. Due to the nature of OAuth and the number of redirects you have, you'd have to send the JWT as a header and pull it out in middleware or store it in a cookie.

If you have configured the feathers-authentication-jwt module to parse the JWT out of a cookie or you are passing it via the Authorization header then you should be able to use the express authenticate middleware that comes bundled with feathers-authentication to process the JWT and load the user into req.user. It does that for you automatically and works just like passport does in that regard.

Let me know if that does or doesn't help. We've had a few people ask about this and we might need to create an example of how to do this.

from authentication-oauth2.

The problem is that this gets called in the callback (e.g. /auth/google/callback) and feathers-authentication-jwt doesn't get a chance to extract the cookie before calling verify. I'm submitting a PR for a possible solution.

from authentication-oauth2.

If you find a solution that would be amazing. This has been a long standing open feature. Let me know if I can help with anything.

from authentication-oauth2.

Well, it works (I've tested it) but it feels kinda kludgey. Give me the day to see if I can pretty it up and make it a bit cleaner.

But overall, the problem is that req.user is undefined because OAuth2 callbacks do not include the proper Authorization header and the verifier does not check cookies. A cleaner fix would be to contain the issue in the verifier.

from authentication-oauth2.

Ok - I now have a cleaner fix that doesn't require any code changes to existing code

from authentication-oauth2.

With cookies enabled and the existing JWT set as feathers-jwt in the cookie, account linking is now possible with @feathersjs/authentication-jwt@^2.0.0 and @feathersjs/authentication-oauth@^1.2.0. Thank you for the fix @nsainaney!

from authentication-oauth2.