Bug 1316266 - java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 4096
Summary: java.security.InvalidAlgorithmParameterException: Prime size must be multiple...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: java-1.7.0-openjdk
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Andrew John Hughes
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1269194
TreeView+ depends on / blocked
 
Reported: 2016-03-09 20:02 UTC by Shakil Siddique
Modified: 2020-01-17 15:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-07 04:15:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shakil Siddique 2016-03-09 20:02:26 UTC 
Description of problem:

With our normal OpenJDK config, we are only able to get encryption working with:
<connection-property name="securityMechanism">9</connection-property> =ENCRYPTED_USER_AND_PASSWORD_SECURITY
<connection-property name="encryptionAlgorithm">2</connection-property> = AES

With 13 set as the securityMechanism, the error below gets tossed to the log on startup.  The full error is attached to the case.
Caused by: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 4096


Version-Release number of selected component (if applicable):

RHEL 6.7
OpenJDK 1.7.0_91
JBoss EAP 6.1.1 (for configuring IBM DB2 datasource)

How reproducible:

Configure DB2 Datasource on JBoss EAP 6.1.1 and set the following:

<connection-property name="securityMechanism">13</connection-property> =ENCRYPTED_USER_AND_PASSWORD_SECURITY
Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.