|
Adding release note component. since it is not sure that this issue will get documented in time for the 10.2 release
For some reason (possibly related to encoding) , the title wasnt showing up in the jira mails, so attempting to copy/paste the title here.
Marking resolved, release note added to 10.2 release notes with revision 448934.
Reopening and reassigning to 10.3, since release note has been added to 10.2.1.
Unsetting Fix Version on unassigned issues.
attaching a patch with the comment added in the server guide. Also attaching the html for convenience. If not comments, I'll commit tomorrow.
Thx Kim, I don't know why I put those extra periods in! but they're gone now; committed with revision: http://svn.apache.org/viewvc?view=rev&revision=543588
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
With IBM 1.4.1 JVM, trying to connect to the server using the derby client with security mechanism 8 (USRSSSBPWD) will result in error
Symptoms:
Connecting using the client driver with security mechanism 8 will throw the following error
ERROR XJ112: Security exception encountered, see next exception for details.
The stack trace will show that the problem is caused by java.security.NoSuchAlgorithmException: SHA1PRNG SecureRandom not available
Cause:
Current USRSSBPWD implementation uses SHA1PRNG algorithm to generate random number(seed) that gets exchanged between client and the server. The SHA1PRNG algorithm is not available with the JCE provider that comes with IBM JVM version 1.4.1.
Workaround:
If you need to use the security mechanism 8, then make sure that support for SHA1PRNG is available in the JCE provider that is available with a particular JVM.
For e.g. Use IBM 1.4.2 JVM that has support for SHA1PRNG or the Sun JVMs.