Authenticating using SASL_OAUTHBEARER
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
I noticed this is not supported. Is there any plan to do this or would you be open to contributions?
It should be straighforward to do. The `config.Net.SASL.TokenProvider` will need to be set. A token provider can be created using https://pkg.go.dev/golang.org/x/oauth2/clientcredentials. The same CA used for the TLS config can also be used to verify the OAuth server. The client credentials flow can be used for this.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named in the issue; start by locating config.Net.SASL.TokenProvider and the existing TLS configuration and authentication setup. Trace how SASL mechanisms are configured, then verify that client-credentials OAuth bearer authentication works and that the TLS CA is applied to the OAuth server connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100