Soap service header signature

Hi @Dino, @Dino-at-Google

Scenario: I am working on migrating the services from DataPower to Apigee. However, XML request payload needs signing before sending it to the backend server?

I have worked on implementing the java callout using this link = https://github.com/DinoChiesa/ApigeeEdge-Java-WsSec-Signature

I have attached the java callout to the proxy request, but the following error is captured in the trace.

Status: Execution Error
Solved Solved
0 2 146
1 ACCEPTED SOLUTION

That callout won't work.

Apigee has changed the restrictions on which Java classes can be used in callouts.

To use WS-Security, you need to use this different callout:

https://github.com/DinoChiesa/ApigeeEdge-Java-WsSec-Signature-2

View solution in original post

2 REPLIES 2

Hi Ashwith,

It is hard to make any useful suggestions on such a generic error message.

If you have an access to On-prem version of Edge, you can use remote debugging while troubleshooting your java callout:

https://apigee.github.io/alfa/edge-dev-javacallout/#11

If you're working in the Cloud, you wound need to fallback to System.out.println() statements to narrow down the line and object that cause the error.

That callout won't work.

Apigee has changed the restrictions on which Java classes can be used in callouts.

To use WS-Security, you need to use this different callout:

https://github.com/DinoChiesa/ApigeeEdge-Java-WsSec-Signature-2