Skip to content
📥 Download as PDF

Troubleshooting

Common issues encountered when integrating with the EUDR SOAP API and their solutions.

WS-Security Authentication Errors

InternalSystemException SOAP fault with no further details

Symptom: The SOAP response contains only:

<env:Fault>
  <faultcode>env:Server</faultcode>
  <faultstring>InternalSystemException</faultstring>
</env:Fault>

No additional error details are returned, and no corresponding entries appear in the server-side logs.

Root cause: The request is being rejected by the WS-Security authentication layer before it reaches the business logic. The most common cause is that the Base64-encoded PasswordDigest and/or Nonce values in the WS-Security UsernameToken header contain extraneous whitespace characters (line breaks, spaces, or carriage returns).

Many Base64 encoding libraries wrap output lines at 76 characters by default (per RFC 2045). When these line breaks are included in the XML element values, the decoded credential no longer matches and authentication fails silently.

How to fix:

  1. Inspect the raw SOAP envelope being sent over the wire (not the in-memory object, but the actual HTTP payload).
  2. Verify that the <wsse:Password> and <wsse:Nonce> element values are single-line strings with no line breaks, carriage returns, or leading/trailing spaces.
  3. Configure your Base64 encoder to produce single-line output without line wrapping.
  4. Ensure no XML pretty-printing or formatting is applied to the Security header after construction.

Example of incorrect values (with line breaks):

<wsse:Password Type="...#PasswordDigest">YWJjZGVm
Z2hpamts</wsse:Password>
<wsse:Nonce EncodingType="...#Base64Binary">bm9u
Y2V2YWx1ZQ==</wsse:Nonce>

Example of correct values (single line, no whitespace):

<wsse:Password Type="...#PasswordDigest">YWJjZGVmZ2hpamts</wsse:Password>
<wsse:Nonce EncodingType="...#Base64Binary">bm9uY2V2YWx1ZQ==</wsse:Nonce>

Note

This error produces no server-side log entries because the request is rejected at the WS-Security authentication interceptor level before any business processing occurs.

Back to top