> I was not exactly suggesting to have AsyncAuthenticationProvider
> extend the current interface :)
Thank you for clarifying. :) You mentioned a bridging class in the
community meeting yesterday, but I misunderstood its implementation.
Your AsyncAuthBridge implementation makes sense to me. The m
On Fri, Sep 3, 2021 at 11:51 AM Michael Marshall wrote:
> The new interface would be called AsyncAuthenticationProvider, and it would
> extend the existing AuthenticationProvider interface. It would have one
> additional method "authenticateAsync" and it would be up to the
> implementation to make
I discussed this feature with Matteo and Addison during yesterday's Pulsar
Community Meeting. Matteo suggested that it might be easier to create a new
interface as part of this work instead of adding a new method to the
existing interface while maintaining backwards compatibility.
The new interfac
Hello Pulsar Community,
Pulsar's current AuthenticationProvider interface only exposes synchronous
methods for authenticating a connection. To date, this has been sufficient
because we have not had any providers that rely on network calls. However,
in looking at the OAuth2.0 spec, there are some c
