You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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!
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
The text was updated successfully, but these errors were encountered: