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.

Sign up for GitHub

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

Jump to bottom

[Bug] Client start failed with error status INTERNAL when not set SessionCredentialsProvider #7391

Closed
3 tasks done
redlsz opened this issue Sep 25, 2023 · 2 comments · May be fixed by #7392
Closed
3 tasks done

[Bug] Client start failed with error status INTERNAL when not set SessionCredentialsProvider #7391

redlsz opened this issue Sep 25, 2023 · 2 comments · May be fixed by #7392
Labels
stale

Comments

@redlsz
Copy link
Contributor

redlsz commented Sep 25, 2023

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

macOS / centos

RocketMQ version

broker -- develop
rocketmq-clients -- master

JDK Version

JDK 8

Describe the Bug

When proxy enable acl but the gRPC client doesn't set SessionCredentials, the client will start failed with INTERNAL error. And an NullPointerException will be thrown at proxy.

client
image

proxy
image

Steps to Reproduce

  1. proxy enable acl (enableACL=true)
  2. statrt gRPC client with no SessionCredentialsProvider set

What Did You Expect to See?

failed with status PERMISSION_DENIED

What Did You See Instead?

status INTERNAL

Additional Context

No response
@redlsz redlsz changed the title [Bug] Bug title [Bug] Client start failed with error status INTERNAL when not set SessionCredentialsProvider Sep 25, 2023
@redlsz redlsz mentioned this issue Sep 25, 2023
Open
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.

@github-actions github-actions bot added the stale label Sep 25, 2024
@github-actions GitHub Actions
Copy link

This issue was closed because it has been inactive for 3 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ISSUE #7391] Fix NPE when parse gRPC authorization header redlsz/rocketmq
1 participant
@redlsz