Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: pulsarctl 3.1 branch can't work with client credentials error #1266

Open
ericsyh opened this issue Nov 26, 2023 · 5 comments
Open

[bug]: pulsarctl 3.1 branch can't work with client credentials error #1266

ericsyh opened this issue Nov 26, 2023 · 5 comments
Labels

Comments

@ericsyh
Copy link
Member

ericsyh commented Nov 26, 2023

Background

I tested and found that pulsarctl 3.1 branch release can't work now which will get error like

pulsarctl topics list public/default
[✖]  client error: could not get client credentials: open : no such file or directory

But I the pulsarctl 3.0 branch works well and won't get this client credentials error.

How to reproduce

I upgraded the pulsarctl on local Mac laptop the version is

Release Version: 3.1.0.2
Git Commit Hash: cb9b6f620364a7cea19325ae2c82523d08265520
Git Branch: HEAD
UTC Build Time: 2023-08-30 09:48:42
Go Version: go version go1.18.10 linux/amd64

Then run any kind of regular commands will get the client crediential error

pulsarctl tenants list
[✖]  client error: could not get client credentials: open : no such file or directory
@ericsyh
Copy link
Member Author

ericsyh commented Nov 26, 2023

@tuteng @zymap @mattisonchao Could you help check this issue?

@ciiiii
Copy link
Member

ciiiii commented Dec 4, 2023

encountered same error

@peica
Copy link

peica commented Dec 23, 2023

change to Release Version: v2.10.5.11-5ce22c is working.

@balticore
Copy link

Same here, when using latest version and client_credentials it fails with error:

client error: authentication failed using client credentials: could not exchange client credentials: AADSTS90014: The required field 'scope' is missing from the credential. Ensure that you have all the necessary parameters for the login request.

However, when downgrading to v2.10.5.11-5ce22c it works without issues.

Not that using service account admin credentials works fine with both version, but we need to use client_credentials to scope operations to particular namespaces and topics.

@zymap
Copy link
Member

zymap commented Feb 20, 2024

@balticore According to the error, do you have the scope in the client credential file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants