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

Kerberos Authentication to Proxy on EventProcessorClient #39566

Open
erdeminanc opened this issue Apr 5, 2024 · 3 comments
Open

Kerberos Authentication to Proxy on EventProcessorClient #39566

erdeminanc opened this issue Apr 5, 2024 · 3 comments
Labels
backlog Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Hubs feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@erdeminanc
Copy link

Query/Question
Currently EventProcessorClient supports Proxy Authentication via Basic and DIGEST. I need to setup the EventProcessorClient behind a corporate secure proxy and I need to authenticate to proxy via Kerberos.

I was able to create a custom HttpClient via implementing HttpClient of Azure and used it in BlobContainerAsyncClient as a result it connected to Blob Storage via using custom HttpClient configured with Kerberos authentication successfully.

I have also implemented HttpClientProvider of Azure and overriden createInstance method where I have returned my custom HttpClient implementation and forced it to use my implementation via setting the environment property like below:

AZURE_HTTP_CLIENT_IMPLEMENTATION: com.*.ApacheHttpClientProvider (full path here - star only for hiding details)

However EventProcessorClient doesn't work and logs below message on onError() callback with the below error message

Error occurred on partition: NONE. Error: java.io.IOException: Attempted read from closed stream.

Why is this not a Bug or a feature Request?
A clear explanation of why is this not a bug or a feature request?

On EventProcessorClient there is no direct call to .httpClient() or Kerberos Authentication under .proxyOptions().

Setup:

  • OS: Windows
  • IDE: IntelliJ
  • Library/Libraries: azure-messaging-eventhubs-checkpointstore-blob :1.19.0, azure-messaging-eventhubs:5.18.0

Information Checklist

  • [ x ] Query Added
  • [ x ] Setup information Added
@erdeminanc erdeminanc changed the title [QUERY] Kerberos Authentication to Proxy on EventProcessorClient Apr 5, 2024
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Hubs needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 5, 2024
Copy link

github-actions bot commented Apr 5, 2024

@anuchandy @conniey @lmolkova

Copy link

github-actions bot commented Apr 5, 2024

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@anuchandy
Copy link
Member

At the moment we’ve only Digest and Basic authentication built in. We’ve a feature request to make the pluggable Proxy contract, so users with need for any specific authentication mechanisms can implement challenge handshaking (e.g., by inspecting proxy-authorization headers, connecting to external token auth-source etc..) for their proxy server and plugin it in.

@anuchandy anuchandy added feature-request This issue requires a new behavior in the product in order be resolved. backlog labels May 28, 2024
@anuchandy anuchandy removed their assignment May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Hubs feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

2 participants