There is no objection, and I will cherry-pick #15121 into branch-2.10 today
Thanks
Yubiao Feng
On Tue, Mar 28, 2023 at 7:52 PM Yubiao Feng
wrote:
> Hi community
>
> ### Summary
> The Admin client (`pulsar-admin`) and Java Client (PulsarAdmin) will throw
> Unauthorized Ex in both scenarios:
> -
+1 (Solution 2)
Thanks,
Bo
PengHui Li 于2023年3月29日周三 09:47写道：
>
> Looks good to me to make it optional in branch-2.10 since we don't want to
> introduce any break behaviors in the subsequent patch releases.
>
> Thanks,
> Penghui
>
> On Tue, Mar 28, 2023 at 9:39 PM Dezhi Liu wrote:
>
> > I agree
Looks good to me to make it optional in branch-2.10 since we don't want to
introduce any break behaviors in the subsequent patch releases.
Thanks,
Penghui
On Tue, Mar 28, 2023 at 9:39 PM Dezhi Liu wrote:
> I agree with cherry-picking PR 15121 to branch-2.10 and keep compatibility.
>
>
> Best,
>
I agree with cherry-picking PR 15121 to branch-2.10 and keep compatibility.
Best,
Dezhi
On 2023/03/28 11:52:06 Yubiao Feng wrote:
> Hi community
>
> ### Summary
> The Admin client (`pulsar-admin`) and Java Client (PulsarAdmin) will throw
> Unauthorized Ex in both scenarios:
> - If there have mo
I agree with cherry-picking PR 15121 to branch-2.10 and keep compatibility.
Best,
Mattison
On Mar 28, 2023, 19:52 +0800, Yubiao Feng
, wrote:
> Hi community
>
> ### Summary
> The Admin client (`pulsar-admin`) and Java Client (PulsarAdmin) will throw
> Unauthorized Ex in both scenarios:
> - If t
Hi community
### Summary
The Admin client (`pulsar-admin`) and Java Client (PulsarAdmin) will throw
Unauthorized Ex in both scenarios:
- If there have more than one broker in a cluster( see issue 1 below ).
- If authentication is enabled for both Pulsar-Proxy and Pulsar-Broker( see
issue 2 below),
