Support OAuth about vertx-web HOT 5 CLOSED

To support OAuth the Resource Server side of things should vertx-auth-service have an api added or extend AuthService to log a user in with just a bearer token? Or should we use the existing api somehow?

from vertx-web.

@pmlopes Do we postpone it to 3.2.0 ? ( I didn't follow the progress, so maybe it's fixed)

from vertx-web.

we postpone because @millross plan is to complete the implementation of vertx3 pac4j and then finish the fully async only OAuth support. (pac4j does way more stuff than just oauth but parts of its API are blocking so he is busy trying to convert some things to async and run other in a worker thread...)

from vertx-web.

Agree with this postponement. Just as an FYI Jérôme (pac4j) has an aspiration to make pac4j optionally non-blocking in future (by offering a non-blocking API and also a plugin client implementation for http requests based on the clients used by the various non-blocking implementations, ie we would offer a vert.x http implementation, for example, as part of the vert.x-pac4j implementation). Depending on what this looks like when we get cracking on it, this may offer a better solution than my vertx-oauth implementation.

I might also look at whether, if that's not viable straightforwardly, separating out some more pac4j stuff so that it can be used conveniently by my OAuth2 implementation, which means every time pac4j add support for a new OAuth2 provider, we can reuse it in the non-blocking implementation, so only the raw "OAuth2" workflow is implemented, and then uses Pac4j configuration for the rest of it. However, that's rather thinking aloud.

from vertx-web.

See https://github.com/vert-x3/vertx-auth/issues/39

from vertx-web.