0

I have a package that I am trying to get through security review. The package is really an API layer that other packages rely on, so it doesn't have a UI you can submit calls through - just global classes other packages can invoke to make requests to the SOAP web services provided by the package.

I got back an email from Security Review team saying the following: "We would need sample http request or good data for the below methods of web service to test individual methods."

Anyone know what that looks like in practice? Should I provide sample code that they could run in the Dev Console that will invoke my global methods that will in turn trigger the callouts? Or are they looking for sample XML they could paste into something like SOAP UI and see what is going on? Anyone navigated something similar through the review process?

Improve this question

1 Answer 1

Reset to default
1

It would be sample XML that they could use in SOAP UI. Please also give them any information necessary for them to craft their own calls.

Improve this answer
2
  • Thanks. In the email, it sounded like they just wanted the param string that gets passed into each method - but do you think they also want the whole SOAP envelope that gets with each callout?
    – BritishBoyinDC
    Jun 4, 2015 at 20:49
  • 1
    Yeah, just give them a trace. They are going to try to make their own calls, so the easier you make it for them, the faster the review.
    – Robert Sussland
    Jun 4, 2015 at 21:02

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .