2016-10-03 29 views
0

我們的Ear應用程序託管在Weblogic 10.3.3服務器上。如何使Weblogic 11gR2(10.3.3)符合FIPS-140

這個程序是用BO 4.1互動,我們現在這個錯誤試圖連接到它:

com.tranme.guide.commonservices.report.InteractionBOException: com.crystaldecisions.sdk.exception.SDKException$ConfidentialChannelFailed: Impossible d'굡blir un canal confidentiel. (FWM 02119) 
cause:com.businessobjects.bcm.exception.FIPSError: Cryptographic library is not FIPS-140-compliant. 
detail:Impossible d'굡blir un canal confidentiel. (FWM 02119) Cryptographic library is not FIPS-140-compliant. 
    at com.tranme.guide.commonservices.report.CrystalReportHelper.getReportInfoObjectsByReportName(CrystalReportHelper.java:515) 
    at com.tranme.guide.notificationmgt.manager.reports.util.ReportManagementTools.getReportInstanceStatuses(ReportManagementTools.java:81) 
    at com.tranme.guide.notificationmgt.manager.reports.util.ReportManagementTools.getGenerationStatusResults(ReportManagementTools.java:51) 
    at com.tranme.guide.notificationmgt.manager.BaseNotificationManager.updateReportGenerationStatus(BaseNotificationManager.java:217) 
    at com.tranme.guide.notificationmgt.business.ejb.impl.NotificationManagementFacadeBeanImpl.updateReportGenerationStatus(NotificationManagementFacadeBeanImpl.java:123) 
    at com.tranme.guide.notificationmgt.business.ejb.impl.NotificationManagementFacadeBeanImpl_z3lp9c_EOImpl.updateReportGenerationStatus(NotificationManagementFacadeBeanImpl_z3lp9c_EOImpl.java:140) 
    at com.tranme.guide.notificationmgt.business.ejb.impl.NotificationManagementFacadeBeanImpl_z3lp9c_EOImpl_WLSkel.invoke(Unknown Source) 
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589) 
    at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) 
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477) 
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) 
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147) 
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473) 
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) 
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) 
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) 
Caused by: com.crystaldecisions.sdk.exception.SDKException$ConfidentialChannelFailed: Impossible d'굡blir un canal confidentiel. (FWM 02119) 
cause:com.businessobjects.bcm.exception.FIPSError: Cryptographic library is not FIPS-140-compliant. 
detail:Impossible d'굡blir un canal confidentiel. (FWM 02119) Cryptographic library is not FIPS-140-compliant. 
    at com.crystaldecisions.sdk.occa.security.internal.ConfidentialChannelService.establishConfidentialChannel(ConfidentialChannelService.java:199) 
    at com.crystaldecisions.sdk.occa.security.internal.ConfidentialChannelService.createConfidentialChannel(ConfidentialChannelService.java:145) 
    at com.crystaldecisions.sdk.occa.security.internal.CCMap.locateCCItem(CCMap.java:63) 
    at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:845) 
    at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:805) 
    at com.crystaldecisions.sdk.occa.security.internal.LogonService.userLogon(LogonService.java:210) 
    at com.crystaldecisions.sdk.occa.security.internal.SecurityMgr.userLogon(SecurityMgr.java:166) 
    at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon_aroundBody0(SessionMgr.java:454) 
    at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon_aroundBody1$advice(SessionMgr.java:512) 
    at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon(SessionMgr.java:1) 
    at com.tranme.guide.commonservices.report.CrystalReportHelper.getSession(CrystalReportHelper.java:156) 
    at com.tranme.guide.commonservices.report.CrystalReportHelper.getReportInfoObjectsByReportName(CrystalReportHelper.java:502) 
    ... 15 more 
Caused by: com.businessobjects.bcm.exception.FIPSError: Cryptographic library is not FIPS-140-compliant. 
    at com.businessobjects.bcm.internal.BcmRsaLib.CheckStartupErrors(BcmRsaLib.java:28) 
    at com.businessobjects.bcm.internal.DHKeyAgreeImpl.<init>(DHKeyAgreeImpl.java:22) 
    at com.businessobjects.bcm.BCM.createKeyAgreement(BCM.java:1080) 
    at com.crystaldecisions.sdk.occa.security.internal.ConfidentialChannelService.establishConfidentialChannel(ConfidentialChannelService.java:175) 
    ... 26 more 

博SDK 11b是在weblogic類路徑(這是我之前的開發決定如何執行他們)。

我已經嘗試過SAP論壇提出的解決方案,但沒有任何運氣。

回答

1

WLS 11G需要配置用於FIPS-compliant SSL connections這些事情:

  • cryptojFIPS.jar添加到PRE_CLASSPATH變量(這樣做類似的東西到什麼SAP論壇suggested
  • 命令行參數-Dweblogic.security.SSL.nojce=true被指定。
  • JVM具有無限強度的JCE(更多詳細信息,請參閱for WLS12C,但步驟相似)。這可能已經設置好了。
+0

在哪個腳本中應該設置類路徑?命令行參數是通過java_options傳遞的?我已經將JVM更新爲去年的另一個案例,因此它已被覆蓋 – Elliot

+0

這是一個環境變量。你可以在shell中設置它,或者如果你喜歡,可以將它放在setWlsEnv.sh中。 –