(OO) Support Tip: OO legacy SOAP API interface does not work with client auth required
When upgrading Central HTTPS security and enabling client authentication (also known as mutual authentication) then the backwards compatible SOAP based API methods will not work if when enabling stricter security from the defaultTomcat configuration the new confirguration is set to clientAuth="true".
The OO server replies with HTTP code 500 message, and the following line in the xml response<faultstring>java.lang.NullPointerException</faultstring>
This is a technical limitation preventing this exact combination of settings to work. The legacy SOAP API is still supported for backwards compatibility. Starting with OO 10.00 OO has a new, well-documented REST base API and we recommend customers and partners to use it. The legacy SOAP API will be deprecated in the distant future.