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
{{ message }}
This repository has been archived by the owner on Feb 9, 2023. It is now read-only.
Hello All,
I'm unable to send authorization with a get request to the end point through robot framework. I succeeded in sending a get request using AWS authorization using Postman. But when I took the signed header and sent it as a dictionary in robot framework it gave me this error:
Create session mysession https://url
${headers}= Create Dictionary Authorization=AWS4-HMAC-SHA256 Credential=, SignedHeaders=content-type;host;x-amz-date, Signature= X-Amz-Date=20210809T065038Z Content_Type=application/json
${response}= Get On Session mysession url=${newActCode} headers=${headers}
HTTPError: 403 Client Error: Forbidden for url: https://
Please help, I'm really stuck.
#robot frame work #aws authorization
The text was updated successfully, but these errors were encountered:
@manoj7410 I don't know. I am using API testing on Robot framework and requests library. And I want to send a request but I must send AWS credentials with it? What do you mean by Google AIY kits?
Hello All,
I'm unable to send authorization with a get request to the end point through robot framework. I succeeded in sending a get request using AWS authorization using Postman. But when I took the signed header and sent it as a dictionary in robot framework it gave me this error:
Create session mysession https://url
${headers}= Create Dictionary Authorization=AWS4-HMAC-SHA256 Credential=, SignedHeaders=content-type;host;x-amz-date, Signature= X-Amz-Date=20210809T065038Z Content_Type=application/json
${response}= Get On Session mysession url=${newActCode} headers=${headers}
HTTPError: 403 Client Error: Forbidden for url: https://
Please help, I'm really stuck.
#robot frame work #aws authorization
The text was updated successfully, but these errors were encountered: