Bug 1316266 - java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 4096
java.security.InvalidAlgorithmParameterException: Prime size must be multiple...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: java-1.7.0-openjdk (Show other bugs)
6.7
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Andrew John Hughes
BaseOS QE - Apps
:
Depends On:
Blocks: 1269194
  Show dependency treegraph
 
Reported: 2016-03-09 15:02 EST by Shakil Siddique
Modified: 2017-02-06 23:15 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-02-06 23:15:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Shakil Siddique 2016-03-09 15:02:26 EST
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.