Forum Discussion

johnrix's avatar
johnrix
Occasional Contributor
11 years ago

SSL Support for REST MockServices in 5.0.0

I'm trying to mock a REST callback in SoapUI 5.0 beta to support an asynchronous callback from my system under test. The callback URL is required to be a secure address. I have configured my SSL setti...
lotus_jp26's avatar
lotus_jp26
New Contributor

Hi John, Have you found a solution for this? I'm using SOAP 5.2.1 and still facing the same issue. Thanks in advance, Padmaja.

  • lotus_jp26's avatar
    lotus_jp26
    New Contributor
    9 years ago

    Hi there,

     

    I was trying to mock a REST services and for some reason it doesn't work with multiple mock actions inside mock service. As long as I point to the path specified in the "Mock service" it works fine.

     

    Also, can you point me to any resources on how to make use of properties/ command line arguments for mock service.

     

    Thanks a lot,

    Regards.

    • nmrao's avatar
      nmrao
      Champion Level 3
      9 years ago
      If the question is not around SSL, please create a separate topic. Avoid cross posts.
  • psy's avatar
    psy
    Occasional Contributor
    8 years ago

    Hello Rao,

     

    same problem for me, too.

     

    The Problem exists now since years and current SoapUI 5.2.1 is still having this issue.

    As a counter test the Ready! API 1.7.0 is working fine with exactly same SoapUI Project. My REST MockUp is reached over SSL Connection.

     

    But I don't want to buy another heavy expensive licence just to be able to Mockup a server.

     

    Most of the time I wish there would be an alternative to that product! :-(

     

    ----

    Edit:

    It would be great if support would mention in such requests, that there is a Feature request open for that

     

    Found here:

    https://community.smartbear.com/t5/SoapUI-NG/SoapUI-REST-Mock-Service-with-SSL/td-p/43051

     

    "

    ......SSL is not currently supported for REST Mock Services. We have a feature request for that to be implemented in a future release (SOAP-2065).

    "