Last updated on SEPTEMBER 16, 2016
Applies to:Oracle Directory Server Enterprise Edition - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
When you log on to the Web Console (DSCC) and you try to manage a proxy server through a web application with "dsee7.war" deployed on an application server such as tomcat, you can select a proxy server to manage but most tabs report "Proxy Server Not Accessible. You must grant access to this server in order to view and edit its configuration."
Clicking "enable access" puts one through various prompts and passwords which all appear to work, but the "Server Not Accessible" message persists.
With ODSEE 18.104.22.168 DPS - dpadm/dpconf runing with Java 7 (delivered with the product) !
==> See Release Notes
5.2 Known Directory Proxy Server Limitations
SSLv2Hello Protocol is Not Enabled in Directory Proxy Server
If you are using Java 7 (which is the default case), the SSLv2Hello protocol is
disabled. So any client trying to negotiate with SSLv2Hello will fail to establish a
connection with Directory Proxy Server. This impacts dpconf and DSCC if they are
using Java 6 and using the SSLv2Hello protocol.
To work around this problem, do one of the following: Run dpconf or DSCC in Java 7,
or enable the SSLv2Hello protocol in Directory Proxy Server.v
See example of deployement:
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