Forum Discussion

GregRESO's avatar
GregRESO
Occasional Contributor
9 years ago

Appears SoapUI NG changes the GET URL provided in Request Tab

Product: Ready! API 1.8.0 (Build Date: 2060715-1722)

Objective: Pull the system's metadata down using OpenID Connect. (Trying to determine if this is a SoapUI issue or an issue with the server I'm trying to connect with.)

 

Start Condition: Successfully logged into the server and received an "Access Token" and "ID Token"

 

I attempted to retrieve the $metadata with: 

GET https://REDACTEDURL.com/sso/reso/odata/$metadata HTTP/1.1

 

 

 

 

I received a 404 error and was instructed by the server developers that I should remove "sso" from the URL

The following is what I received:

 

 

Things that I noticed when I changed the tool to submit: 

GET https://REDACTEDURL.com/reso/odata/$metadata HTTP/1.1

 

1: The tool actually submitted the following:

GET http://REDACTEDURL.com/sso/login HTTP/1.1

2: The https: was changed to http:

3: The URL included in the Endpoint and Resource fields do not match what's in the GET statement. "/reso/odata/$metadata" was changed to "/sso/login"

 

QUESTION: Is the changing of the GET statement an issue with the SoapUI tool or the server I'm trying to connect with?

 

Thanks, Greg

 

  • GillerM's avatar
    GillerM
    9 years ago

    Mike here from SoapUI NG side.  Not sure what's going on at the API layer, but you can double check in:

     

    > Log on bottom left > Look in HTTP log

     

    This will tell you if there's any 302 redirects or other factors at play here

  • bhodges's avatar
    bhodges
    Visitor
    9 years ago

    I am one of the developers working with GregRESO on this from the server side.  Have there been any insights into what might be wrong here?

    • GregRESO's avatar
      GregRESO
      Occasional Contributor
      9 years ago

      I haven't heard from anyone on this yet.

       

      Thanks, Greg

  • GillerM's avatar
    GillerM
    Staff
    9 years ago

    Mike here from SoapUI NG side.  Not sure what's going on at the API layer, but you can double check in:

     

    > Log on bottom left > Look in HTTP log

     

    This will tell you if there's any 302 redirects or other factors at play here

    • GregRESO's avatar
      GregRESO
      Occasional Contributor
      9 years ago

      I found the link to the "Logs" at the bottom of the screen. Reviewing the HTTP logs. Found a HTTP 302. I'll work with the API developers.

       

      Thanks, Greg