Search Engine: Elastic

Article ID: 132343, created on Mar 7, 2018, last review on Mar 7, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 7.3


After upgrade OA 6.x to OA 7.x attempts to switch to Billing fail.


The UI uses a privacy proxy to connect to the Billing node:

09:16:12.983 [default task-89] DEBUG c.p.p.c.e.b.billing_manager.BMHelper - Connection through proxy:

Upgrade to OA 7.0 requires Management Node and Billing appliation server to be migrated to RHEL/Centos 7, which use newer SSL/TLS libraries and Billing settings do not support outdated SSL protocols by default:

[root@pbafe01 ~]# grep SSLProtocol /etc/httpd/conf.d/0ssl.conf
SSLProtocol all -SSLv2 -SSLv3 -TLSv1

On teh other hand, the proxy is running under Centos 5, which does not support newer TLS:

[root@linupps01 ~]# rpm -qa | grep openssl

[root@linupps01 ~]# rpm -qa | grep curl

[root@linupps01 ~]# cat /etc/issue
Red Hat Enterprise Linux Server release 5.6 Beta (Tikanga)


Either disable proxy to connect to Billing at OA > System > Settings > System Properties > Use proxy for connection to Business Automation or install the privacy proxy node with the new OS and reregister it in OA.

dd79f16c76b9dca75205ab5e9f5465ea caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 0871c0b47b3b86ae3b1af4c2942cd0ce 31987597efff5a3a9ce779cc203bbe5e 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF