Remove JSSE from Ricoh ESA and stop supporting Java 3 device.
Incident Properties
Question
Hi RiDP support,
This is a continuation of Incident #5000: DO RICOH SDKS GET AFFECTED BY ORACLE NEW LICENSING MODEL?.
We are planning on removing all Oracle Java SE usage from Kofax Ricoh ESA combined client.
Ricoh ESA is being built for JVM 1.3. It uses and packages JSSE 1.3.3 libraries in the client package for secure communication.
We are going to remove JSSE libs from Ricoh ESA, and replace them with the implementation in JDK 1.4. Thus, the generated class files will be specified for JVM 1.4 version.
From your POV, could you please advise:
- Is this solution feasible? Is there any potential compatibility issue?
- Although SDK/J is now in minimum support, is the end of support for Java 3 devices acceptable?
Any advice would be greatly appreciated.
Thank you.
Do Ricoh SDKs get affected by Oracle new licensing model?
Incident Properties
Question
Hi RiDP support,
Oracle has changed their license model recently.
We would like to know if Ricoh SDKs, both SKD/J and SmartSDK, get affected by Oracle new license model.
- Do the SDKs depend on any Oracle Java SE versions?
- If they do, are these Oracle Java SE versions under the new license?
- Does Ricoh have a license to re-distribute Oracle Java SE?
Some additional information from Oracle:
- https://www.oracle.com/technetwork/java/javaseproducts/javasesubscription-data-sheet-4891969.pdf
- https://www.oracle.com/technetwork/java/javaseproducts/overview/javasesubscriptionfaq-4891443.html
- https://blogs.oracle.com/java-platform-group/a-quick-summary-on-the-new-java-se-subscription
Thank you.
Production sign SLNX_Management_Extension for sdk/J
Incident Properties
Question
please product sign this dmext sdk/j application
Production sign SLNX_Management_Extension for sdk/J
Incident Properties
Question
Please product sign the slnx management servelt for sdk/J
RICOH ESA COMBINED CLIENT 7.7.5.74 production package is expired after 14 days.
Incident Properties
Question
Hi RiDP support,
On May 19, we no longer can install the production-signed package of Ricoh ESA combined client from this incident https://ricoh-ridp.com/ridp/support-system/incident/ricoh-sdc-canada/1683813488/1901235634/4911. We receive error code 201.
If we set the device date/time back to May 18, we can install it.
The package was signed on May 5, so it seems like the package is expired after 14 days.
Could you please help to check the package?
I attach both the production-signed package from last time and the unsigned package in case we need to re-sign it.
Notes:
- The package needs to be signed with both SHA and SHA256 to support old models.
- Sign everything, including some previously signed 3rd party libraries.
Thank you.
MAINTENANCE SIGNATURE REQUEST FOR RICOH ESA COMBINED CLIENT 7.7.5.74
Incident Properties
Question
Hi RiDP Support,
We are releasing a fix for a customer.
Could you please help sign the maintenance signature for the attached client using both SHA1 and SHA256?
Thank you.
MAINTENANCE SIGNATURE FOR IMFP 1.5.12
Incident Properties
Question
Hi there,
Please find the attached zip,
We have done a bug fix and updated the version from 1.5.11 to 1.5.12 in our Pharos iMFP solution. Please provide the signed bundle.
Note: this build includes the Bouncy Castle Provider libraries, as you updated us, this jar has issues that were already signed that were creating a problem while dev signing for 14 days. Please have a reference for lastly signed version request for iMFP application.
https://ricoh-ridp.com/ridp/support-system/incident/ricoh-sdc-canada/1653931635/1529823054/4562.
Let us know if anything else is required from our end.
Thanks!
Pharos iMFP for Ricoh not working with all java version showing exception with Bouncy provider library
Incident Properties
Question
Hi there,
Our Ricoh iMFP solution is not working with All available JRE versions and shows exceptions related to the Bouncy Provider library. We have tested different versions and got the following error while running our application.
ricoh.rxop.rxcommon.RxopException: -- init -- JCE cannot authenticate the provider BC
at ricoh.rxop.rxinst.RicohJavaDevice.e(RicohJavaDevice.java)
at ricoh.rxop.rxinst.RicohJavaDevice.access$000(RicohJavaDevice.java)
at ricoh.rxop.rxinst.gc.run(gc.java)
at ricoh.rxop.rxinst.cf.run(cf.java)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.SecurityException: JCE cannot authenticate the provider BC
at javax.crypto.Cipher.getInstance(Cipher.java:664)
at javax.crypto.Cipher.getInstance(Cipher.java:599)
at ricoh.rxop.rxcommon.t.a(t.java)
at ricoh.rxop.rxcommon.r.a(r.java)
at ricoh.rxop.rxcommon.r.<init>(r.java)
at ricoh.rxop.rxcommon.DeviceInfoList.<init>(DeviceInfoList.java)
at ricoh.rxop.rxcommon.DeviceInfoList.getInstance(DeviceInfoList.java)
... 5 more
Caused by: java.util.jar.JarException: file:/C:/Users/Administrator/Downloads/iMFP%20for%20Ricoh%20v1.5.10%20GR%20-%20RxOP%203.8.1/iMFP%20for%20Ricoh%20v1.5.10%20GR%20-%20RxOP%203.8.1/Install/lib/bcprov-jdk14-152.jar has unsigned entries - org/bouncycastle/LICENSE.class
at javax.crypto.JarVerifier.verifySingleJar(JarVerifier.java:510)
at javax.crypto.JarVerifier.verifyJars(JarVerifier.java:371)
at javax.crypto.JarVerifier.verify(JarVerifier.java:297)
at javax.crypto.JceSecurity.verifyProviderJar(JceSecurity.java:164)
at javax.crypto.JceSecurity.getVerificationResult(JceSecurity.java:190)
at javax.crypto.Cipher.getInstance(Cipher.java:660)
... 11 more
Below are the details of the device which got used for testing.
Model: RICOH MP C307, System: 1.24, Web Image Monitor:1.14, Installed JavaTM Platform version: 12.78.00
We have used the following JRE environment while testing-
jre-8u301, jre-8u341, jre-8u351, jre-8u361, jre-9.0.4, jre-10.0.2, jdk-18.0.1.1
It worked for jre-8u301, jre-8u341, jre-9.0.4, jre-10.0.2 and shows exception with others
Could you please help us to understand why the Bouncy Provider library is showing different behaviors with different versions of JRE?
Accordingly, we would be checking this with our customer and specifying the JRE version that would need to install while using our pharos Ricoh iMFP solution.
Let me know if you need anything from our end.
Thanks!
Demo dev signed bundles iMFP 1.5.11
Incident Properties
Question
Hi there,
we are looking for demo-signed bundles to provide to the customer for testing our iMFP solution. We have used the demo signature link provided over the ridp portal (https://ricoh-ridp.com/forms/signatureservices/demo-signature), and from that applications got installed but with a stop status. Please find the attachment.
for your reference there is an old incident, we have shared the build for certification and faced the same issue.
https://ricoh-ridp.com/ridp/support-system/incident/ricoh-sdc-canada/1653931635/1529823054/4562.
Could you please help us to resolve this issue and provide the demo signed bundles to us?
Please find the attached zip files for demo/beta signing. Let us know if you have any questions.
Thanks!
Request access to tools from development
Incident Properties
Question
Hello, my name is Leonardo and I have a problem accessing HOME»PLATFORMS»SDK/J»GETTING STARTED access to the following pages is blocked Development Materials and ESA Emulator even with the premier plus plan, could you tell me why access is blocked and grant me access?