Netcracker / Netcracker/qubership-testing-platform-itf-executor
Implement new authentication for Kafka on ITF
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 2
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe
No response
Describe the solution you'd like
Hi team,
As a part of Test Automation services on Telenet account we might face the cases that we need to integrate with Telenet Kafka service in scope of stubs implementation activities.
sasl.mechanism=GSSAPI
user data is stored in keyTab (which is configured by IT team)
Example of configs:
security.protocol=SASL_PLAINTEXT
sasl.kerberos.service.name=kafka
sasl.mechanism=GSSAPI
sasl.jaas.config=com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
storeKey=true
keyTab="/path/to/keytab/{keytab_name}.keytab"
principal="{userPrincipalName}@mail.domain.com"
Describe alternatives you've considered
No response
Additional information
Example of code on TOMS side:
Contributor guide
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
The issue names no source files, tests, or entry points. Start by locating the executor’s Kafka integration and configuration handling, then compare its supported authentication options with the supplied SASL/GSSAPI keytab settings and TOMS example. Done should include a defined implementation scope and a way to verify Kafka authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- authentication, distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100