(aws-msk-alpha): Cannot provide my own encryption key for SASL Scram authentication
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- aws, kafka, typescript
- Domain
- authentication, cloud
Research direction
Start in packages/@aws-cdk/aws-msk/lib/cluster.ts and follow ClientAuthentication.sasl through the addUser entry point. Check how saslScramAuthenticationKey is initialized and confirm that a provided key is retained; done means addUser no longer reports that an authentication KMS key is missing when one was supplied.
Written by the indexing model from the issue text.
Description
Describe the bug
ClientAuthentication.sasl properties currently allow you to provide an encryption key for the user secret. However, the construct does not leverage that key.
Current code for authentication configuration:
clientAuthentication: ClientAuthentication.sasl({
scram: true,
key: props.kmsEncryptionKeyForCredentialsSecret,
})
Then, add user:
this.cluster.addUser(user)
Expected Behavior
It will use the encryption key I provide.
Current Behavior
It does not use the encryption key, nor creates new one.
It throws an error: Cannot create users if an authentication KMS key has not been created/provided.
Reproduction Steps
See above.
Possible Solution
Initialize this.saslScramAuthenticationKey with the provided key, if set.
https://github.com/aws/aws-cdk/blob/main/packages/%40aws-cdk/aws-msk/lib/cluster.ts
Additional Information/Context
No response
CDK CLI Version
2.45
Framework Version
No response
Node.js Version
16.15.1
OS
MacOS
Language
Typescript
Language Version
No response
Other information
No response
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 71
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.
More from aws/aws-cdk
-
@aws-cdk/aws-bedrock-agentcore-alpha bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
@aws-cdk/aws-rds effort/small feature-request p2
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
@aws-cdk/aws-cloudwatch effort/medium feature-request p2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
@aws-cdk/aws-s3-deployment bug p2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
@aws-cdk/aws-lambda-nodejs effort/medium feature-request p2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100