-
Notifications
You must be signed in to change notification settings - Fork 21
Add auth and docker documentation #348
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR improves documentation around OIDC authentication and Docker containerization for the confluent-kafka-javascript library. The changes provide clearer guidance on authentication methods and Docker setup best practices.
- Enhanced OIDC documentation to clarify support for both
client_credentials
andjwt_bearer
grant types - Rewrote Docker Alpine documentation with updated Node.js version and clearer instructions for handling platform-specific binaries
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
INTRODUCTION.md | Updated OIDC authentication section to clarify grant types and add jwt_bearer documentation reference |
examples/node-rdkafka/docker-alpine.md | Complete rewrite of Docker documentation with modern Node.js version and better binary handling instructions |
Comments suppressed due to low confidence (1)
examples/node-rdkafka/docker-alpine.md:1
- [nitpick] The filename suggests this is Alpine-specific documentation, but the title and content now cover general Docker usage. Consider renaming the file to 'docker.md' or updating the title to reflect Alpine-specific content.
# Dockerfile for confluent-kafka-javascript
@@ -1102,7 +1102,10 @@ const producer = new Kafka().producer({ | |||
}); | |||
``` | |||
|
|||
For a special case of OAuthBearer token authentication, where the token is fetched from an OIDC provider using the `client_credentials` grant type, the library provides a built-in callback, which can be set through just the configuration without any custom function required: | |||
For a special case of OAuthBearer token authentication where the token is fetched from an OIDC provider using the `client_credentials` or `jwt_bearer` grant type, the library provides a built-in mechanism for authentication. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing comma after 'authentication'. Should be: 'For a special case of OAuthBearer token authentication, where the token is fetched from an OIDC provider using the client_credentials
or jwt_bearer
grant type, the library provides a built-in mechanism for authentication.'
For a special case of OAuthBearer token authentication where the token is fetched from an OIDC provider using the `client_credentials` or `jwt_bearer` grant type, the library provides a built-in mechanism for authentication. | |
For a special case of OAuthBearer token authentication, where the token is fetched from an OIDC provider using the `client_credentials` or `jwt_bearer` grant type, the library provides a built-in mechanism for authentication. |
Copilot uses AI. Check for mistakes.
Improve documentatoin around OIDC and dockerization