VisualBean edited a comment on issue #92:
URL: https://github.com/apache/pulsar-dotpulsar/issues/92#issuecomment-950636235
It appears there are 2 flows according to one of the original Pulsar
creators Matteo Merli.
There is the AuthenticationProvider, which that's sends a request to the
client to re-validate the token when it is about to expire.
And if this is not supported by the client or the token is allowed to
expire, the broker will close the TCP connection.
For posterity, the Java client looks something like this
```java
PulsarClient client = PulsarClient.builder()
.serviceUrl("pulsar://broker.example.com:6650/")
.authentication(
AuthenticationFactoryOAuth2.clientCredentials(issuerUrl,
credentialsUrl, audience))
.build();
```
With the internals found here
https://github.com/apache/pulsar/blob/ac5114f8944784972b831438f8c7e0cbd57db4e5/pulsar-client/src/main/java/org/apache/pulsar/client/impl/auth/oauth2/AuthenticationOAuth2.java#L40
For an idiomatic .net experience, I would probably still be more inclined to
opt for the delegate.
Is this something you see easily implemented in the current state of the
dotpulsar client?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
