SDK/J

Hi RiDP support,

We are releasing a new version for the Ricoh ESA combined client to address the following bug:

- 2095072: Client could not display print job list.

Could you please help sign the maintenance signature for the attached package?

Notes:

- To support old models, the package needs to be signed with both SHA and SHA256.

- Sign everything, including some previously signed 3rd party libraries.

Thank you.

Hi

Please help to add maintenance signature to the attached application.

- This version is re-branched name from "Kofax" to "Tungsten Automation", and updated new logo.

- Severity Vulnerabilities: Upgrade commons-httpclient-3.1.jar to commons-httpclient-3.1-redhat-3.jar .

Thank you

Ngoc

Hi RiDP,

We have an issue with installation of Ricoh PCC 4 (an ESA client) on SP C440DN.

We have tried to install the client via:

- Device web portal.

- RXOP (using remote operation client 1.6.5 - RXOP 3.8.9)

but not working.

With device web portal, device displays empty "Extended Feature List"

No error in Rlog.

With RXOP, it throws -- install -- ERR_OTHER :: DalpFile is not found from ZipFile. ::  ::  :: 

The package can be installed on other devices such as C2004 or C3003.

On the SP C440DN, we can install another SDK/J xlet.

Could you please advise us on how to troubleshoot/address this issue?

Check attached for clients, device info.

Thank you.

Hi RiDP support,

We are releasing a new version for the Ricoh ESA combined client to address the following bug:

- 2087900: Client could not transfer scan job if the server uses self-signed certificate.

It has the same version number as ticket #5186 on purpose.

Could you please help sign the maintenance signature for the attached package?

Notes:

- To support old models, the package needs to be signed with both SHA and SHA256.

- Sign everything, including some previously signed 3rd party libraries.

Thank you.

Hi RiDP support,

This is a high priority request.

We are releasing a new version for the Ricoh ESA combined client to address the following bug:

- 2087860: Could not transfer scan job intermittently.

Could you please help sign the maintenance signature for the attached package?

Notes:

- To support old models, the package needs to be signed with both SHA and SHA256.

- Sign everything, including some previously signed 3rd party libraries.

Thank you.

Hi

We have an attempt to fix version to provide demo on the customer side

But the demo signature could not start the app, although it is installed success on C3003/IM C2004

Starting the app gets error J501.

We get demo from this link: https://ricoh-ridp.com/forms/signatureservices/demo-signature

We can run unsigned app on the Ricoh Simulator.

This is log 125 of the issue:

[stdout] [SDK_P_SM___] [Domain] Can not mapping: cancelStartApp
[stdout] [SDK_P_XLETM]initXlet() - Kofax MFP Client
[SDK_P_XLETM]statechange exception === [stderr] java.lang.ExceptionInInitializerError
[stderr]     at com.kofax.des.mfp.client.ricoh.MFPClient.<clinit>(MFPClient.java:119)
[stderr]     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[stderr]     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[stderr]     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[stderr]     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
[stderr]     at jp.co.ricoh.dsdk.osgi.service.multiXletManager.XletManager.handleRequest(Unknown Source)
[stderr]     at jp.co.ricoh.dsdk.osgi.service.multiXletManager.XletStateQueue.dispatchEvents(Unknown Source)
[stderr]     at jp.co.ricoh.dsdk.osgi.service.multiXletManager.XletStateQueue$1.run(Unknown Source)
[stderr]     at java.lang.Thread.run(Thread.java:682)
[stderr] Caused by: java.lang.SecurityException: invalid SHA1 signature file digest for jp/co/ricoh/dsdk/framework/panel/IPAddressEditSet$CancelActionListener.class
[stderr]     at sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:671)
[stderr]     at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:334)
[stderr]     at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:256)

I think we got an signature issue for SDK J app.

Please help to re-create a valid demo signature for the attached file.

Thank you

Ngoc

Hello,

We recently had applied for the Ricoh PTECT compatibility testing. and we had to postpone it due to some code changes we had to make. So our question is, If our certification is cancelled and if we reapply then how the payment is handled? Do you refund the payment or do you hold it for our next certification attempt? This is the PO number: 230742.  Please advise. 

Thank you,

nQ Zebraworks

Hi RiDP Support,

We are releasing a new version for the Ricoh ESA combined client.

This version addresses some insecure third-party libraries.

Could you please help sign the maintenance signature for the attached package?

Notes:

- To support old models, the package needs to be signed with both SHA and SHA256.

- Sign everything, including some previously signed 3rd party libraries.

Thank you.

We did apply for the Ricoh Compatibility Testing Request certification but then we realized we have to do some code changes so we would like to hold on to our existing application, so may I know where could I track my existing application? 

Thank you,