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

Secrets with special characters are not correctly parsed #642

Open
oscerd opened this issue Mar 22, 2021 · 1 comment
Open

Secrets with special characters are not correctly parsed #642

oscerd opened this issue Mar 22, 2021 · 1 comment

Comments

@oscerd
Copy link
Contributor

oscerd commented Mar 22, 2021

Hello

As example take this: https://github.com/oscerd/kamelet-samples/tree/master/aws-sqs-sink

If the secret key contains character like "/" or "+" the parsing will fail and the authentication will fail.

"[1] 2021-03-22 06:21:38,457 ERROR [io.qua.run.Application] (main) Failed to start application (with profile prod): software.amazon.awssdk.services.sqs.model.SqsException: The security token included in the request is invalid. (Service: Sqs, Status Code: 403, Request ID: xxxxxxxxxxx, Extended Request ID: null)"

This happens with camel-k 1.3.1, k-runtime 1.6.0 and quarkus 1.5.0

Even adding RAW({{secretKey}}) in the aws-sqs-sink.kamelet.yaml gives the same result.

cc @lburgazzoli

@squakez
Copy link
Contributor

squakez commented May 25, 2021

I have tried to reproduce this with a basic timer-log kamelet, and I did not manage to reproduce the issue. I can read the secret values when any base64 + or / chars are present. The link you've posted is 404 now. Would you mind to post the way to reproduce the issue? thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants