How to resolve error:Failure due to insufficient maximum key length according to the installed JCE jurisdiction policy files.

How to resolve error:Failure due to insufficient maximum key length according to the installed JCE jurisdiction policy files.

book

Article ID: KB0076219

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for Database 7.2.0,8.x

Description

When below JDBC URL is used as in ActiveMatrix Database Adapter configuration or JDBC URL configuration in TIBCO ActiveMatrix BusinessWorks Plug-in for Database "jdbc:tibcosoftwareincoracle://localhost:1521;serviceName=orcl.apac.tibco.com;EncryptionLevel=required;EncryptionTypes=AES256;DataIntegrityLevel=required;DataIntegrityTypes=MD5"

Then the following error may occure:
Exception : java.sql.SQLException: [tibcosoftwareinc][Oracle JDBC Driver]Failure due to insufficient maximum key length according to the installed JCE jurisdiction policy files. Please install "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files at tibcosoftwareinc.jdbc.oraclebase.ddcr.b(Unknown Source) at tibcosoftwareinc.jdbc.oraclebase.ddcr.a(Unknown Source)
at tibcosoftwareinc.jdbc.oraclebase.ddcq.b(Unknown Source)
at tibcosoftwareinc.jdbc.oraclebase.ddcq.a(Unknown Source)
at tibcosoftwareinc.jdbc.oracle.OracleImplConnection.a(Unknown Source)
at tibcosoftwareinc.jdbc.oracle.OracleImplConnection.b(Unknown Source)
at tibcosoftwareinc.jdbc.oracle.OracleImplConnection.aa(Unknown Source)
at tibcosoftwareinc.jdbc.oraclebase.BaseConnection.b(Unknown Source)
at tibcosoftwareinc.jdbc.oraclebase.BaseConnection.k(Unknown Source)
at tibcosoftwareinc.jdbc.oraclebase.BaseConnection.b(Unknown Source)
at tibcosoftwareinc.jdbc.oraclebase.BaseConnection.a(Unknown Source)
at tibcosoftwareinc.jdbc.oraclebase.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at com.tibco.adapter.adb.database.DBConnectionManager.getDBConnection(Unknown Source)
at com.tibco.adapter.adb.core.ADBAdapter.testConnection(Unknown Source)
at com.tibco.adapter.adb.core.ADBAdapter.onInitialization(Unknown Source)
at com.tibco.sdk.MAppImpl.initialize(MAppImpl.java:563)
at com.tibco.sdk.MDefaultAppImpl.start(MDefaultAppImpl.java:144)
at com.tibco.sdk.MApp.start(MApp.java:225)
at com.tibco.adapter.adb.core.ADBAdapter.main(Unknown Source) 

Issue/Introduction

How to resolve the issue Failure due to insufficient maximum key length according to the installed JCE jurisdiction policy files. Please install "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files at tibcosoftwareinc.jdbc.oraclebase.ddcr.b(Unknown Source) at tibcosoftwareinc.jdbc.oraclebase.ddcr.a(Unknown Source)

Environment

=================================================== Product: TIBCO ActiveMatrix BusinessWorks Plug-in for Database Version: 7.2.0 ,8.x OS: All Supported Operating Systems ====================================================

Resolution

To resolve the issue follow the below steps:

[A] Update policy files:
1)  Download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8.
 https://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
2)  Uncompress and extract the downloaded file.
    This will create a subdirectory called jce.
    This directory contains the following files:
        README.txt                   This file
        local_policy.jar             Unlimited strength local policy file
        US_export_policy.jar         Unlimited strength US export policy file
3)   Copy and replace for JCE jurisdiction policy JAR files in:
        TIBCO_HOME/<tibcojre>or<tibcojre64>/lib/security/           [Unix]
        TIBCO_HOME\<tibcojre>or<tibcojre64>\lib\security\           [Windows]
4)  Then restart the designer and test the connection.

[B] As well as another solution is:
Update the JDBC URL as:
jdbc:tibcosoftwareinc:oracle://Servername:portnumber;ServiceName=Servicename;DataIntegrityLevel=accepted;EncryptionLevel=accepted;EncryptionType=AES256;DataIntegrityLevel=required;DataIntegrityTypes=MD5