Closed
Bug 317479
Opened 19 years ago
Closed 18 years ago
Modify JSS tests to use IBM JCE on AIX platform
Categories
(JSS Graveyard :: Tests, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
4.2.3
People
(Reporter: Sandeep.Konchady, Assigned: Sandeep.Konchady)
References
Details
Attachments
(1 file)
23.00 KB,
patch
|
alvolkov.bgs
:
review+
glenbeasley
:
superreview+
|
Details | Diff | Splinter Review |
Some JSS tests are hard coded to use SunJCE provider independent of the platform. This may not be the case on all platforms (AIX). Need to test for JDK/Platform specific JCE provider, which in case of AIX is IBM.
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•19 years ago
|
||
There are many issues here, not just the provider. [1] java.security.NoSuchProviderException: no such provider: SunRsaSign at java.security.Security.getAlgClassName(Security.java:606) at java.security.Security.getImpl(Security.java:1081) at java.security.KeyPairGenerator.getInstance(KeyPairGenerator.java:210) at org.mozilla.jss.tests.KeyFactoryTest.genPrivKeyFromSpec(KeyFactoryTest.java:135) at org.mozilla.jss.tests.KeyFactoryTest.doTest(KeyFactoryTest.java:118) at org.mozilla.jss.tests.KeyFactoryTest.main(KeyFactoryTest.java:104) [2] java.security.NoSuchProviderException: No such provider: SunJCE at javax.crypto.e.a(Unknown Source) at javax.crypto.Mac.getInstance(Unknown Source) at org.mozilla.jss.tests.HMACTest.doHMAC(HMACTest.java:65) at org.mozilla.jss.tests.HMACTest.main(HMACTest.java:122) [3] java.security.NoSuchAlgorithmException: Algorithm SunX509 not available at javax.net.ssl.SSLSecurity.a(Unknown Source) at javax.net.ssl.KeyManagerFactory.getInstance(Unknown Source) at org.mozilla.jss.tests.JSSE_SSLServer.getServerSocketFactory(JSSE_SSLServer.java:214) at org.mozilla.jss.tests.JSSE_SSLServer.main(JSSE_SSLServer.java:125) [4] ============= Start JSSE client tests The java class is not found: com/sun/net/ssl/internal/ssl/Provider
Assignee | ||
Comment 2•18 years ago
|
||
Based on my observation, it was easier to check for JDK vendor instead of AIX for using IBMJCE. The reason is that IBM produces JDK for Linux and Windows too. So if the vendor is IBM, then use IBMJCE.
Attachment #211404 -
Flags: superreview?(glen.beasley)
Attachment #211404 -
Flags: review?(alexei.volkov.bugs)
Assignee | ||
Updated•18 years ago
|
Target Milestone: --- → 4.2.3
Comment 3•18 years ago
|
||
Yes, we use the IBM JDK on Linux.
Comment 4•18 years ago
|
||
Comment on attachment 211404 [details] [diff] [review] Added check for java.vendor=IBM Corporation to use IBMJCE This looks good, I would make Sun the default then IBM.
Attachment #211404 -
Flags: superreview?(glen.beasley) → superreview+
Updated•18 years ago
|
Attachment #211404 -
Flags: review?(alexei.volkov.bugs) → review+
Assignee | ||
Comment 5•18 years ago
|
||
Checking in org/mozilla/jss/tests/JSSE_SSLServer.java; /cvsroot/mozilla/security/jss/org/mozilla/jss/tests/JSSE_SSLServer.java,v <-- JSSE_SSLServer.java new revision: 1.7; previous revision: 1.6 done Checking in org/mozilla/jss/tests/JSSE_SSLClient.java; /cvsroot/mozilla/security/jss/org/mozilla/jss/tests/JSSE_SSLClient.java,v <-- JSSE_SSLClient.java new revision: 1.7; previous revision: 1.6 done Checking in org/mozilla/jss/tests/HMACTest.java; /cvsroot/mozilla/security/jss/org/mozilla/jss/tests/HMACTest.java,v <-- HMACTest.java new revision: 1.2; previous revision: 1.1 done Checking in org/mozilla/jss/tests/KeyFactoryTest.java; /cvsroot/mozilla/security/jss/org/mozilla/jss/tests/KeyFactoryTest.java,v <-- KeyFactoryTest.java new revision: 1.4; previous revision: 1.3 done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 6•18 years ago
|
||
I have tested the latest test suite from the tip today on Red hat RHEL4. It works and got a 100% success rate with IBM JDK 5.0 after installing unrestricte policy files (local_policy.jar, US_export_policy.jar).
Assignee | ||
Comment 7•18 years ago
|
||
*** Bug 325517 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•