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
I'd like to perform SigV4 signed requests with tokens / temporary credentials. This usually involves two steps:
Request to get the credentials / token (e.g. from AWS STS or Cognito Identity Pool)
Actual request(s), signed with the credentials retrieved in step 1
Currently I'd have to do this as two hurl calls in a wrapper script.
Proposal
This would be easy to achieve if username/password could be set from variables, for example
POST request#1
[Captures]
session_access_key_id: jsonpath "$.foo"
session_secret_key: jsonpath "$.bar"
POST request#2
[Options]
username: {{session_access_key_id}}
password: {{session_secret_key}}
aws-sigv4: aws:amz:foo:bar
I imagine this could be implemented easily (I could try to come up with a PR), but I don't fully grasp potential side effects on [BasicAuth] yet (see also #898).
This would also allow to set username/password from HURL_foo environment variables, which improves security (no credentials in the shell history and in system-wide process list).
What would be great additionally: If variables persisted across hurlfiles, so that I could use hurl --test login.hurl request1.hurl request2.hurl, as maintaining a large number of tests in one hurlfile feels cumbersome (might be worth a separate issue).
The text was updated successfully, but these errors were encountered:
Problem to solve
As follow-up to #1844 (thanks!) –
I'd like to perform SigV4 signed requests with tokens / temporary credentials. This usually involves two steps:
Currently I'd have to do this as two
hurl
calls in a wrapper script.Proposal
This would be easy to achieve if username/password could be set from variables, for example
I imagine this could be implemented easily (I could try to come up with a PR), but I don't fully grasp potential side effects on
[BasicAuth]
yet (see also #898).This would also allow to set username/password from
HURL_foo
environment variables, which improves security (no credentials in the shell history and in system-wide process list).What would be great additionally: If variables persisted across hurlfiles, so that I could use
hurl --test login.hurl request1.hurl request2.hurl
, as maintaining a large number of tests in one hurlfile feels cumbersome (might be worth a separate issue).The text was updated successfully, but these errors were encountered: