Comcast / Comcast/pulsar-client-go
support kerberos authentication?
- Dominant language
- Go
- Stars
- 79
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
The issue only asks whether Kerberos authentication should be supported and provides no files, tests, entry points, alternatives, or acceptance criteria. First determine how authentication is currently handled in this Go Pulsar client, then establish the required Kerberos behavior and tests before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100