Does EPM to Support TLS 1.2 Communication via OHS?
(Doc ID 2179810.1)
Last updated on FEBRUARY 03, 2019
Applies to:Hyperion Planning - Version 18.104.22.168.00 to 22.214.171.124.005 [Release 11.1]
Hyperion BI+ - Version 126.96.36.199.00 to 188.8.131.52.702 [Release 11.1]
Hyperion Financial Data Quality Management, Enterprise Edition - Version 184.108.40.206.220 to 220.127.116.11.220 [Release 11.1]
Information in this document applies to any platform.
For those customers who do not have an SSL Offloader like an F5 this process can be used.
This article contains a work-around for using TLS 1.2 with EPM 18.104.22.168. Testing was performed using EPM 22.214.171.124 but this should also work with earlier EPM 11.1.2.X versions.
EPM 126.96.36.199 includes OHS version 188.8.131.52. This version of OHS supports only TLS 1.0. For customers requiring TLS 1.2, the following work-around can be used.
Once implemented the communication request flow will look like the following:
User -- SSL(TLSv1.2 ) --> OHS 184.108.40.206/mod_proxy --SSL(TLSv1.0) --> OHS 220.127.116.11/mod_wl_ohs --SSL or HTTP --> WLS Managed server(s).
This document is an adaptation (specific to an EPM use case) from the OHS document Doc ID 1920143.1
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