TLS 1.2 Doesn't support by the ohs which come along the binary till
22.214.171.124. didn't check 11.2.
If you are planning for 126.96.36.199 you need to have another ohs on top of
installed binary ohs to have TLS 1.2.
We have SSL at ohs level and able to connect through maxl. We don't use
add-in but I guess will be fine with add-in as well.
On Wed 8 Jul, 2020, 12:52 AM community-admin, <
Thanks for the reply
Yes, to implement SSL at OHS using TLS 1.2 communication, we need to look at a workaround. I found which may help in achieving it.
However, with SSL at OHS layer in place , what additional steps we need to execute to make Essbase connections also secure. I have made port 6423' active during initial Essbase configuration. But i see 6423 is not listening on the sever when I check it through netstat.
Another query is , with SSL enabled at OHS layer with TLS 1.2. , will it have any performance impact or latency when the users access the system ?
Can anyone provide some info on this please ?
Impact or network latency depends on many factors which can't be predicted
Your SSL port is not listening bcoz you have not enable SSL yet.
Better I can suggest to go for development and apply changes and intimate
On Thu 9 Jul, 2020, 6:52 PM community-admin, <