Account Number Encryption working incorrect
Hi ,
Account number encryption is not working in JBOSS (Pega 7.2).
However, it is working for Websphere server.
When executed in JBOSS, the activity is generating different encrypted account number every time hence the decryption results incorrect value later.
Did anyone face a similar issue or has any idea why this is happening ? An immediate assistance is needed on it.
Thanks!
Accepted Solution
Cognizant
IN
Hi All,
The difference in JBoss and Websphere was related to secure random algorithm.
JBoss by default picks NativePRNG whereas Websphere's IBMSecureRandom uses SHA1PRNG.
Due to this difference the Hash Code generated in JBoss is different each time and remains constant in Websphere.
We hard coded the algorithm name in our java function which fixed our issue.
Thanks!
Pegasystems Inc.
IN
Hi Kumar,
Can you let me know how you have implemented this encryption in Pega i.e, Have you used any customized encryption or if you have used any OOTB feature for encryption kindly mention
Is account number is one of the blob column?
Cognizant
IN
Hi Prasanth,
We have created a function to do the encryption. We are using standard java classes such as SecureRandom, KeyGenerator with AES encryption for the same.
Pegasystems Inc.
AU
Hi Kumar,
Hope you are using JCE (Java Cryptography Extension) for the encryption. Could you please verify the Java versions being used in JBOSS and WAS instances? Also check the JCE jar files placed in the two server instances class path whether they are same and using same encryption?
Regards,
Basavaraj
Cognizant
IN
Hi Basavraj
the java version being used in Webshpere is jdk-1.7.0 and for jbos is jdk-1.7.0_9.
Does this makes any difference?
Also ,I tried debugging the code, found a difference in SecureRandom object.
The algorithm being used in Jboss for Secure random is NativePRNG and for Websphere its - IBMSEcureRandom.
Let me know if this information help.
Pegasystems Inc.
AU
Hi Kumar,
I think there is a difference in the random bytes generated if both uses different providers (sun and ibm). However I am not sure about the same, we will wait for the inputs from subject matter expert.
Regards,
Basavaraj
Accepted Solution
Cognizant
IN
Hi All,
The difference in JBoss and Websphere was related to secure random algorithm.
JBoss by default picks NativePRNG whereas Websphere's IBMSecureRandom uses SHA1PRNG.
Due to this difference the Hash Code generated in JBoss is different each time and remains constant in Websphere.
We hard coded the algorithm name in our java function which fixed our issue.
Thanks!