Skip to content
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

decryptbytes: procdecryptdata: The parameter is incorrect when consuming using api keys in the command #2412

Open
natalia-ramos-bzy opened this issue Nov 10, 2023 · 4 comments
Assignees
Labels
bug Something isn't working stale This ticket hasn't have activities for a period of time.

Comments

@natalia-ramos-bzy
Copy link

There's an error when consuming a topic using api keys in the command

confluent kafka topic consume <topicName> --from-beginning --schema-registry-api-key <srApiKey> --schema-registry-api-secret <srApiSecret> --api-key <kafkaApiKey> --api-secret <kafkaApiSecret> --environment <env> --cluster <cluster>
Error: failed to create consumer: decryptbytes: procdecryptdata: The parameter is incorrect.
confluent - Confluent CLI

Version:     v3.40.0
Git Ref:     299e722ef
Build Date:  2023-11-02T23:32:56Z
Go Version:  go1.21.0 X:boringcrypto (windows/amd64)
Development: false
@MuweiHe
Copy link
Contributor

MuweiHe commented Nov 13, 2023

Hi, we received a similar issue where it was fixed by creating a new pair of api-key. You may want to try that and see if it can resolve the issue for now. I'll continue investigate. The issue is probably in the process of encrypting/decrypting credentials using windows dpapi.

@MuweiHe
Copy link
Contributor

MuweiHe commented Nov 13, 2023

There's very limited info we could get on this issue. I will do a release this week to add more traces/logs in this command, and can you provide me the output / traces you see using the newer version so I can debug further? Will comment here when the new version is out

@MuweiHe
Copy link
Contributor

MuweiHe commented Nov 30, 2023

hi @natalia-ramos-bzy are you still seeing this issue? You may want to update to latest cli release, and run the same command with --unsafe-trace. Please provide me without the logs output and that will help us investigate. Thanks!
Please send a message to [email protected] including your logs

@natalia-ramos-bzy
Copy link
Author

Hi @MuweiHe I'm using v3.42.0 and I'm still having this issue. However I was unable to send the traces in an email:
image

@brianstrauch brianstrauch added the bug Something isn't working label Jan 11, 2024
@MuweiHe MuweiHe added the stale This ticket hasn't have activities for a period of time. label Jan 22, 2024
@MuweiHe MuweiHe self-assigned this Jan 22, 2024
@sajjadlateef sajjadlateef assigned sgagniere and unassigned MuweiHe Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale This ticket hasn't have activities for a period of time.
Projects
None yet
Development

No branches or pull requests

4 participants