lhotari commented on PR #509: URL: https://github.com/apache/pulsar-helm-chart/pull/509#issuecomment-2834968564
@brunodomenici @gulecroc In addition to plain OIDC provider support, there would be a need to handle broker-to-broker and proxy-to-broker authentication. The foundations for this is described in the Pulsar docs at [Enable Custom OpenID Connect Integration with Kubernetes](https://pulsar.apache.org/docs/4.0.x/security-openid-connect/#enable-custom-openid-connect-integration-with-kubernetes). It's also possible to use static JWT tokens for broker-to-broker authentication while enabling OIDC auth, but the problem with that type of solution is that there's no current way to prevent using JWT tokens from outside of the cluster. A possible leak of the "superuser" token would be a problem. That's why it would be recommended to replace superuser tokens completely with Kubernetes OIDC provided tokens. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
