Hi,
Would PIP 55 propose how the client side plugin can implement a
credential/token refresh mechanism? The use case would be the client
proactively refresh the bearer token before disconnected due to expiration
by the broker.
I am thinking some additions to Authentication/AuthenticationDataProv
The main issue is how the changes in that PR interact with mutual
authentication system like SASL/Kerberos which were already
introduced in 2.4. The renew/renewed mechanism would have to work with
auth-challenges and responses.
Instead, I have changes that are built on top of that AuthState
abstra
Hi,
We have the same ask and we had created PR to address the issue last year
with the PR: https://github.com/apache/pulsar/pull/3705
Thanks,
Rajan
On Tue, Jan 14, 2020 at 3:21 PM Matteo Merli wrote:
>
> https://github.com/apache/pulsar/wiki/PIP-55%3A-Refresh-Authentication-Credentials
>
> ---
https://github.com/apache/pulsar/wiki/PIP-55%3A-Refresh-Authentication-Credentials
-
## Goals
Enhance the Pulsar Authentication framework to support credentials that
expire over time and need to be refreshed by forcing clients to
re-authenticate.
Typical examples are:
*
