Document algorithm support
required for using secmec 8(USRSSSBPWD) and limitation on ibm141 vm.
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
[
http://issues.apache.org/jira/browse/DERBY-1867?page=comments#action_12436620 ]
Sunitha Kambhampati commented on DERBY-1867:
--------------------------------------------
Problem:
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.
>
Document algorithm support required for using secmec 8(USRSSSBPWD) and
limitation on ibm141 vm.
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-1867
> URL: http://issues.apache.org/jira/browse/DERBY-1867
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Affects Versions: 10.2.1.0
> Reporter: Sunitha Kambhampati
> Fix For: 10.2.1.0
>
>
> Using secmec8 with ibm141 vms fails with
> java.security.NoSuchAlgorithmException : SHA1PRNG. This needs to be
> documented in the server guide.
> Please see:
> http://issues.apache.org/jira/browse/DERBY-1788?page=comments#action_12432124
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
