000034936 - Error "Could not compute secret" when initializing RSA Data Protection Manager client 3.5.2.4

Document created by RSA Customer Support Employee on Mar 21, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000034936
Applies ToRSA Product Set: Key Manager
RSA Product/Service Type: Token Client Java
RSA Version/Condition: 3.5.2.4
IssueUnable to initialize a DPM client running in a J2EE web application under WebLogic. Following error is logged:
INFO token.audit.c[?] - 1.1.1.2.3 13: Created SSL Context with Provider: RsaJsse 
WARN token.debug.a[?] - Unable to establish stable server connection to server: dpm1.domain.com:443,Error:Could not compute secret.
WARN token.debug.a[?] - Unable to establish stable server connection to server: dpm1.domain.com:443,Error:Could not compute secret.
WARN token.audit.i[?] - 1.2.3.1.1 1.5: Client registration failed
ERROR ErrorCode: 40032 on index:[0] ErrorMessage(s): ErrorMessage(s): Client registration failed, reason: client.app_name specified in the properties parameter may be is already in use. Could not compute secret.

 
CauseWebLogic uses RSA BSAFE for its own cryptographic operations, and will load its own Crypto-J classes first. When the DPM client in the webapp is initialized it may pick an older version of Crypto-J, generating unexpected behavior and errors.
ResolutionInclude the following in your web application under WebApp/WEB-INF/weblogic.xml to force the web app to use its own jar file for class loading:
<?xml version="1.0" encoding="UTF-8"?> 
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
  <context-root>dpm-webapp</context-root>
  <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
  </container-descriptor>
</weblogic-web-app>

 

Attachments

    Outcomes