Configuration SSL for DFC on client

LakeAlex

Hi All.

I installed DFC on client computer and configured dfc.properties with

dfc.session.secure_connect_default=secure

clientX = new DfClientX();docbrokerClient = clientX.getDocbrokerClient();

Here exception occurs:

docbaseMap = docbrokerClient.getDocbaseMapFromSpecificDocbroker(null, sHost, sPort);

How to properly configure the server?

Thanks.

$exception {"DfDocbrokerException:: THREAD: main; MSG: [DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker \"dde66:1489\" failed; ERRORCODE: ff; NEXT: null:DfDocbrokerException:: THREAD: main; MSG: [DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker \"dde66:1489\" failed; ERRORCODE: ff; NEXT: null\r\n\tat com.documentum.fc.client.DfDocbrokerException.newRequestFailedException(DfDocbrokerException.java:12)\r\n\tat com.documentum.fc.client.impl.docbroker.DocbaseMapBuilder.getMapFromSpecificDocbroker(DocbaseMapBuilder.java:75)\r\n\tat com.documentum.fc.client.impl.docbroker.DocbrokerClient.getDocbaseMapFromSpecificDocbroker(DocbrokerClient.java:182)\r\nCaused by: DfDocbrokerException:: THREAD: main; MSG: [DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker \"dde66:1489\" failed; ERRORCODE: ff; NEXT: null\r\n\tat com.documentum.fc.client.DfDocbrokerException.newRequestFailedException(DfDocbrokerException.java:12)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.DocbrokerConnection.<init>(DocbrokerConnection.java:30)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.DocbrokerConnectionFactory.newDocbrokerConnection(DocbrokerConnectionFactory.java:27)\r\n\tat com.documentum.fc.client.impl.docbroker.MapBuilder.issueRequest(MapBuilder.java:27)\r\n\tat com.documentum.fc.client.impl.docbroker.DocbaseMapBuilder.getDataFromDocbroker(DocbaseMapBuilder.java:63)\r\n\tat com.documentum.fc.client.impl.docbroker.DocbaseMapBuilder.getDataFromDocbroker(DocbaseMapBuilder.java:58)\r\n\tat com.documentum.fc.client.impl.docbroker.DocbaseMapBuilder.getMapFromSpecificDocbroker(DocbaseMapBuilder.java:71)\r\n\t... 1 more\r\nCaused by: DfIOException:: THREAD: main; MSG: [DM_SESSION_E_RPC_ERROR]error: \"Server communication failure\"; ERRORCODE: 100; NEXT: null\r\n\tat com.documentum.fc.client.DfIOException.newCommunicationFailureException(DfIOException.java:16)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.newDocbrokerRpcClient(NetwiseDocbrokerRpcClientFactory.java:39)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.DocbrokerConnection.<init>(DocbrokerConnection.java:25)\r\n\t... 6 more\r\nCaused by: java.net.ConnectException: Connection timed out: connect\r\n\tat java.net.PlainSocketImpl.socketConnect(Native Method)\r\n\tat java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)\r\n\tat java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)\r\n\tat java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)\r\n\tat java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)\r\n\tat java.net.Socket.connect(Socket.java:519)\r\n\tat com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:549)\r\n\tat com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:141)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.openSSLSocket(NetwiseDocbrokerRpcClientFactory.java:381)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.createTimedSocket(NetwiseDocbrokerRpcClientFactory.java:170)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.access$200(NetwiseDocbrokerRpcClientFactory.java:28)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory$1.run(NetwiseDocbrokerRpcClientFactory.java:143)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory$1.run(NetwiseDocbrokerRpcClientFactory.java:124)\r\n\tat java.security.AccessController.doPrivileged(Native Method)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.openSocket(NetwiseDocbrokerRpcClientFactory.java:121)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.openSocket(NetwiseDocbrokerRpcClientFactory.java:70)\r\n\tat com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.newDocbrokerRpcClient(NetwiseDocbrokerRpcClientFactory.java:35)\r\n\t... 7 more\r\n"} System.Exception {System.Runtime.InteropServices.COMException}

Find more posts tagged with

Comments

DCTM_Guru

When you installed Content Server, did you install Secure connection port/service? Read Content Server Admin guide, under Setting Secure Connection Mode for more info.

LakeAlex

Thank you.

I found the following in the "Content Server Enterprise Edition Installation Guide 6.6":

Permit or require secure SSL connections

Client applications can connect to Content Server through a standard native port or through a secure

port that uses Secure Sockets Layer (SSL) for encryption. During repository configuration, you are

asked what type of connection clients will use to connect to the repository. The choices are:

• Native — Content Server listens for client connection requests only on ports that are not SSL ports.

Content Server refuses requests for a secure connection.

• Secure — Content Server listens for client connection requests only on a secure SSL port. The

client and Content Server do not use SSL authentication to authenticate each other. However,

the information exchanged between the client and Content Server is encrypted. Content Server

refuses connection requests other than SSL connections.

• Native and secure — Content Server accepts both native and secure connection requests.

Note: This feature is only available with a Trusted Content Services license, which you need to

obtain separately.

Is it true that if I did not install the Trusted Content Services then I cannot use SSL with DFC?

Will I always get an exception on calling sessionManager.getSession(docbase);?

Thanks

DCTM_Guru

Note sure. The Note reference was not in Content Server 6.5 Admin manual.

LakeAlex

I am sorry. It seems I have incorrectly understood you.

But I don't understand why the Content Server installer allows selecting native, secure or dual options if It is not supported without additional license which user has skipped.

I also found in the Object_Reference_6.5.pdf:

secure_connect_mode string(16) S The type of port on which the server is

listening. Valid values are:

native, meaning an unsecure port secure, meaning a secure port (using SSL)

dual, meaning both a native and a secure port

Non‑trusted servers do not use this property.

They accept only native connections.

OK, thank you.

I found the following in the Content Server Administration Guide:

To change the secure connection mode for the server, reset the secure_connect_mode

property in the server’s server config object. You can use Documentum Administrator

or DQL to reset the secure_connect_mode property. You must restart the server after

resetting the secure_connect_mode property

Now I attempt to run Documentum Administrator - It does not work too.

I have installed Content Server in secure mode.

However, in dfc.properties file I see dfc.docbroker.port[0] as 1489 instead 1490.

And dfc.session.secure_connect_default=try_secure_first

Note that the netstat shows only 1490 port.

I change in dfc.properties port to 1490 and restart server. Unfortunatelly, Docbrocker log shows the following:

EMC Documentum Connection Broker (version 6.6.0.041 Win32)
(c) Copyright EMC Corp., 1994 - 2010
Fri Feb 11 11:39:31 2011 843000 [DM_DOCBROKER_I_START]info: "Docbroker has started. Process id: 1156"
Fri Feb 11 11:39:31 2011 890000 [DM_DOCBROKER_I_REGISTERED_PORT]info: "The Docbroker registered using port (1490)."
Fri Feb 11 11:39:31 2011 890000 [DM_DOCBROKER_I_LISTENING]info: "The Docbroker is listening on network address: (INET_ADDR: family: 2, port: 1490, host: DDE66 (192.168.0.188, bc00a8c0))"
nl_accept() failed. Recovering docbroker...

nl_accept() failed. What does it mean?

I cannot run the Documentum Administrator using link http://server:9080/da

Have you any idea, please?

Thanks