This project is read-only.

IPAWS signature not valid

Jul 16, 2013 at 11:00 PM
We are trying to use IPAWSTester to submit CAP 1.2 into IPAWS. All the test cases work except for POST which returns error 308 "signature not valid". We have followed the instructions for conversion of the JKS key into P12 and the certificate doesn't seem to be the problem (given that Ack, Get, etc work fine). Further, our IPAWS contact confirms that the signed payload embedded in the SOAP is indeed valid. Their suggestion is that something in EDXLSharp is changing something AFTER the SOAP message is built completely, but before it is actually posted.

We built the project from sources v3.1 (i.e., the latest not marked 'unstable').

Anyone has experienced anything similar? Thanks.
Sep 23, 2013 at 10:11 PM
There are some differences between v3.1 and unstable that deal with the canonicalization of the message. Additionally, the friendly name of the FEMA certificates changed slightly. A patch will be added to v3.1 shortly to address these differences.