Jared Hanson

Update: I've published [email protected] to npm, which includes the ability to pass `Strategy` instances directly to `passport.authenticate()`. This version was based on a smaller PR #739. I consider this use...

Yeah, that's the objective. Standardizing the claims so they are in the IANA registry would be the ideal outcome. The specification (once finalized) could be submitted to the most relevant...

Can you point me to the documentation that indicates OAuth 2.0 is usable for user-based login flows? I looked the docs over, but as far as I can tell OAuth...

In general, I don't make commitments as to if or when I will do open source work. That work is driven based on my own interests or needs. I'm interested...

Thanks for this feedback, it helps me understand the desire for OAuth 2.0. One thing I want to clarify, however: > My main motivation for wanting to implement Auth 2.0...

What's the benefit to splitting this between the client and server and passing a code between the two? Why not just handle it all from the server-side?

You are covering a lot of topics in this issue, and there's a lot of incorrect statements. To start with, this library is not abandoned. Next, you say that state...

> My apologies for not being familiar with the history of this library. If it works, that is still opt in, and according to https://www.passportjs.org/tutorials/google/state/ it is supposed to happen...

It would help me if you could clearly articulate if you are reporting an issue, or just struggling with integrating this package into your application. In the filing of this...

Have you called `passport.use()` to configure [passport-oauth2](https://www.passportjs.org/packages/passport-oauth2/)?