VWS/beServiceTrigger Support For HTTPS
(Doc ID 2813755.1)
Last updated on OCTOBER 25, 2021
Applies to:Oracle Communications Network Charging and Control - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (NCC), 220.127.116.11.0 version,
Customer intend to use HTTPS with Open Services Development (OSD) to secure incoming connections for external API calls. There is a radio button that switches OSD to use HTTPS, and Data Access Pack (DAP) has some certificate configuration for this as well. However this is a full switchover, there is no way to allow HTTP and HTTPS, so if it's switched then everything must support it.
How one can secure this from the Voucher and Wallet Server (VWS)?
Also the Real-Time Wallet Notifications (RTWN) will go via beServiceTrigger at present. This is primarily due to the renewal logic for periodic charges containing all the information required, and these must go via beServiceTrigger. Furthermore, beServiceTrigger has built in loadsharing across all the Service Logic Controllers (SLCs), whereas they believe DAP requires a load balancer. One cannot see any configuration for beServiceTrigger - How can this be achieved? Alternatively if the SLC was capable of store and deliver and this was a feature of notification submission this would simplify matters somewhat? If it were possible to specify on a port by port basis, then customer could choose to secure traffic on port X for external API calls, but leave unsecured from the VWS on port Y.?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document