apache/pulsar

Make Java Client Authentication Asynchronous

Open

#19,429 创建于 2023年2月5日

在 GitHub 查看
 (13 评论) (0 反应) (0 负责人)Java (13,697 star) (3,485 fork)batch import
Stalearea/clientgood first issuehelp wantedtype/enhancement

描述

Search before asking

  • I searched in the issues and found nothing similar.

Motivation

The OAuth2 client's authenticate call is blocking, which is not great for the client, and is bad for the proxy because the proxy authenticates from a netty event loop.

Solution

In the same way that PIP 97 #12105 make the AuthenticationProvider async, we should update the Authentication interface.

Alternatives

No response

Anything else?

This change will likely require a PIP. I am unable to write such a PIP at this time, so I am creating this issue to keep track of this missing feature.

Are you willing to submit a PR?

  • I'm willing to submit a PR!

贡献者指南

技术栈
java
领域
backendauthentication
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
JavaAsynchronous programmingPulsar authentication model
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
Examine the existing `Authentication` interface in the Pulsar repository (e.g., pulsar client/src/main/java/org/apache/pulsar/client/api/Authentication.java) and the async `AuthenticationProvider` introduced in PIP 97 (#12105). Understand the current blocking authenticate call and identify how to convert it to a completable future. Review the linked PIPs and comments in issue #19429 for design discussions. Consider that this change may require a new PIP; study the process for proposing PIPs in Apache Pulsar.