IT29943: API GATEWAY SERVICE EXPECTS X509 CERTIFICATE WITHOUT LINEBREAKS

APAR status

• Closed as program error.

Error description

• The user created an app in API Connect Portal and noticed that
  the format of the x509 certificate pasted into the
  "Certificate" field in the Portal can affect mTLS success.
  Case 1: The user provides the certificate in the following
  format:
  -----BEGIN CERTIFICATE-----
  CERTIFICATE_IN_B64_FORMAT_ON_ONE_LINE
  -----END CERTIFICATE-----
  Everything works fine, the app is created and the API can be
  invoked using the correct client id and the provided
  certificate.
  Case 2: The user provides the certificate in the following
  format (so with CR/LF or LF line breaks):
  -----BEGIN CERTIFICATE-----
  CERTIFICATE_DATA_LINE_1 CRLF
  CERTIFICATE_DATA_LINE_2 CRLF
  CERTIFICATE_DATA_LINE_3 CRLF
  ....
  -----END CERTIFICATE-----
  The App is created but when trying to invoke the API with the
  correct client id and client certificate you receive:
  {
  "httpCode": "401",
  "httpMessage": "Unauthorized",
  "moreInformation": "Client certificates for mutual TLS in the
  API request doesn't match the registered certificate."
  }
  

Local fix

• Ensure the base64 encoded certificate does not have any
  linefeeds (CR/LF or LF) but is a one-liner.
  

Problem summary

• The fix now allows newline characters.
  

Problem conclusion

• The fix is in 2018.4.1.7
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DATAPOWER

• Fixed component ID

  DP1234567

Applicable component levels