Commverse MMSC Cartridge - https Certificate Validation
Last updated on JULY 19, 2017
Applies to:Oracle Communications ASAP Cartridges - Version 1.0.0 and later
Information in this document applies to any platform.
When the MMSC cartridge was upgraded to support version 3.5, one of the requirements was to support HTTPS. In implementing HTTPS, it was requested that when the HTTPS session was established from the cartridge that any validation errors be ignored.
The customer preference is to retain the behavior implemented in UNICO Mediator where certificate validity is ignored and removes the need to maintain a trusted a valid certificate.
It however seems this is not implemented (ignoring the errors). The solution appears to have been to provide a "default certificate" which actually includes the certificate from the MMSC. This allowed the the connection to be established and removed the need to ignore any of the validation errors and meant that the request to ignore the validation was not implemented.
This was discovered recently when the MMSC was upgraded from version 3.5 to version 4.0. Customer was unable to establish a connection to the MMSC as the certificates did not match.
The expected behavior is that when the network element is upgraded and there are certificate changes on the network element that there be no impact to the MMSC cartridge.
This means no additional steps be performed when an upgrade is performed on the network element.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms