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

Authority header in Service-to-Service invocation(gRPC) not being set correct #4620

Closed
rabollin opened this issue May 16, 2022 · 3 comments
Closed
Labels
stale Issues and PRs without response

Comments

@rabollin
Copy link
Contributor

Authority header in the Service-Service invocation request is set to “{daprappId}.{namespace}.svc.cluster.local” . The ask is how to get :authority header to be the same as resolved DNS name. ex: “{daprappId}.dapr”

the authority header that is being updated when the message is posted by the dapr sidecar of processor app is handled by GO. [[meta]: authority issues · Issue #4717 · grpc/grpc-go (github.com)] (grpc/grpc-go#4717) - This is an open issue on how GO/GRPC handles authority header and the scope for improvement.

@rabollin rabollin added the kind/bug Something isn't working label May 16, 2022
@yaron2 yaron2 removed the kind/bug Something isn't working label May 16, 2022
@yaron2
Copy link
Member

yaron2 commented May 16, 2022

Removing kind/bug as this is not a bug.

You can set the header with the grpc.WithAuthority option: https://pkg.go.dev/google.golang.org/grpc#WithAuthority.
As this is not (and should not be) configurable in Dapr, you'd need to make these changes to daprd here:

opts := []grpc.DialOption{

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale Issues and PRs without response label Jul 15, 2022
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues and PRs without response
Projects
None yet
Development

No branches or pull requests

3 participants