Forum Discussion

sprice090161's avatar
sprice090161
Contributor
5 years ago

Has anyone actually been able to execute a POST or a GET Using AWS

I have spent at least a year working with Customer Support and Dev on the most basic of REST calls POST/GET to AWS. It does not work.  The first ticket that I entered I performed a sid by side test u...
  • richie's avatar
    richie
    5 years ago
    Hey sprice090161,

    I apologise if i misunderstood and went off at a tangent trying to help resolve your issue.....my ADHD tends to make for poor concentration occasionally.

    Short answer! :) Yes i was hitting AWS early last year.

    I think there's something really weird going on with your use case anyway, it looks like you have a couple of what appear to be additional commas at the ends of your SignedHeaders and Credential header values and a Content-Type: application/json header which would be superfluous i would've thought considering this is on a GET with no payload.

    Cheers!

    Rich
sprice090161's avatar
sprice090161
Contributor

Here is the initial case that I submitted.  There was a defect found as I said before  pertaining the dynamic generation of the header value.

 

From Customer Support

"Development has created a defect of RIA-11463 for this issue as the x-amz-security-token header isn't signed in the AWS signature. "

 

Case: 00352931
Status: Researching
Priority Level: High
File Upload Link: http://smartbear.secure.force.com/support/WebToCaseFileUploadS3?caseId=5001O00001WBuWM

Case Description:
I want to execute a simple HTTP test step that accesses our API's in the AWS cloud. I manually load into our application and using th edev tools in chrome, I copy the current session AccessCode, SecretCode, and Security Token, along with region and service names, which are fixed.

This works perfectly using "Postman". However it wont work in soapUI.

From either the Resource Request for the http (defined via url) test step, or by adding an http test step to an existing test cases.

The server url and endpoint are defined correctly.
The AWS aut has been selected and defined with active credentials.
Run the step and it fails as if the token has expired and yet they are new (We have a 1 hour timeout on the session token)

<Fault xmlns="https://dev.api.newforma.cloud/v1/actionitems">
   <type>https://newforma.com/apierrors/bad_request</type>
   <title>The security token included in the request is invalid.</title>
   <message>The security token included in the request is invalid.</message>
   <requestId>ac2ab76c-8300-11e9-83a7-71b7c2a6db53</requestId>
</Fault>

Exact data as in the HTTP log file. The ready API log is empty

Here is the Raw Request: as you can see the correct headers are all being generated.
GET https://dev.api.newforma.cloud/v1/actionitems HTTP/1.1
Accept-Encoding: gzip,deflate
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Authorization: AWS4-HMAC-SHA256 Credential=ASIAWUJEERKJR6XIZ46F/20190530/us-east-1/execute-api/aws4_request, SignedHeaders=content-type;host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=cdce4c69a83ae140baab47d6869a98fe014e33adb4c9515c2a31292d097ff02f
x-amz-date: 20190530T173052Z
content-type: application/json
Content-Length: 0
Host: dev.api.newforma.cloud
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.5.2 (Java/1.8.0_181)
*****************************************

No there is yet another ticket because after this build was installed allowing me to perform a POST, I'm still not able to perform a get for the reason I mentioned earlier. You can search AWS for the bug that I later referenced in the subsequest ticket.
 
I'm not asking you folks in the community to trouble shoot and solve the problem. I'm trying to understand if anyone has been successfull executing requests against there api's located up in the AWS cloud. 
 
 
 
richie's avatar
richie
Community Hero
5 years ago
Hey sprice090161,

I apologise if i misunderstood and went off at a tangent trying to help resolve your issue.....my ADHD tends to make for poor concentration occasionally.

Short answer! :) Yes i was hitting AWS early last year.

I think there's something really weird going on with your use case anyway, it looks like you have a couple of what appear to be additional commas at the ends of your SignedHeaders and Credential header values and a Content-Type: application/json header which would be superfluous i would've thought considering this is on a GET with no payload.

Cheers!

Rich
  • sprice090161's avatar
    sprice090161
    Contributor
    5 years ago

    No Worries....Thank you for taking th etime to answer :-)