SDK/J

Hello,
 

Please find attached version 6.0.8 of the PaperCut SDK/J application. It fixes the following issues:

- Fixed an issue that prevented that prevented the panel sleep mode from being locked when using card readers

The application supports SDK 4/5/7/10/11/12 on uWVGA, WVGA and SVGA.

Please Note:

• The attached ZIP was built and signed using our development product ID (which is different to our official product ID). After it has been built and tested I have modified the product ID in the DALP file to be the official product ID, removed the dev signature by removing all files under pc-ricoh-client.jar\META-INF\ and created a new ZIP which is attached. We have tested the embedded app installs and functions correctly prior to these changes.
• On our last maintenance signature it was mentioned that we are now outside the scope of the maintenance period. I noticed in the newest Comaptibility QA Testing Program form (v4 010119) the period has now changed to 36 months since last certification. We are within that new maintenance period. Is this new period applicable for our SDK/J solution?

Thanks,
Daniel

Hello

I create this incident for SDK/J application full certification.

In progression of full certification:

(1) For Purchase Order + Compatibility Logo and Production Signature Program, do we use old templete from 2018? or can you give me new templates?

(2) We will ship to you a flash memory includes a VMware 11 of KTA 7.6 server. KofaxRicoh client - SDK/J app should connect to this KTA 7.6 server. Please give us your address that you can receive the flash memory.

The VMware KTA 7.6 is used for both SDK/J app and SmartSDK app.

(3) Next week, we will attached to this incident  KofaxRicohClient-SDK/J app + a quick setup guide for VMware machine + Kofax Ricoh Client guide + List fix bugs/changes on the client.

Please inform me if I was missing something.

Thank you very much

Ngoc

What is the model code for these devices?
IM 350F
IM 430F
IM C3500
IM C4500
IM C5500

On Windows 2016 servers, we are finding that the self-signed server certificate is generating the following java exception:

java.lang.RuntimeException: Could not generate DH keypair

My limited resarch into this issue seems to indicate that the server is generating a certificate that has a larger keypair size than the java runtime on the Ricoh device can handle. Have you run into this before? Are there steps I can take to allow java runtime to work with larger keypairs, or is my only choice to force the server to generate certificates based on a smaller keypair size?

Thanks in advance for any suggestions you might have.

Dale Hunt

Software Developer IV

Open Text

Hello,

Well, almost immediately after we submitted our Ricoh SDK/J application for maintenance certification, we had to fix two defects that required further updates to our Java application. I'm submitting this request using the information that we provided in the previous request for maintenance certification. Please don't hesitate to contact me if more information is required:

1. List of supported platforms : SDK/J Version 10.x, 11.x, 12.x

2. Supported Display Panels: uWVGA, WVGA

3. The only modified .jar file is RightFax.jar

4. .dalp file version is 11.0.6

Overview of bug fixes: There were no changes to the User Interface

1. The application data connection to rightfax was modified to use a less-priviledged account when connecting as a guest.

2. The application data connection was modified to allow ssl certificate errors to be ignored, as per solution provided in incident report -> https://ricoh-ridp.com/ridp/support-system/incident/ricoh-americas-corp-technology-center/1554725071/332020816/3299

As before, no releases notes for specific modules/applications included with RightFax

We previously reuqested a maintenance signature on this product but we were unable to install the signed package. I think this was caused by a bad build on our part. I've rebuilt the same package and tested that it installs correctly with a beta signature. Could we please get a maintenance signature on the attached application? The details of this package are identical to case #3103

Hello

We are going to send our unsigned Ricoh clients for KTA 7.6 to Ricoh for full certification.

1.   KofaxRicohClient SDK/J:  We plan to send the Ricoh Xlet app for full certification in the week on 22 April, 2019.

2.   KofaxRicohClient SmartSDK:  We plan to send the Ricoh Android app for full certification on 02 May, 2019.

Both 2 clients use the same server environment (KTA 7.6).

We would like to get the both signed Ricoh clients by the end of May, 2019, is it posible to RiDP/PTEC?

How about  RiDP/PTEC plan?

Please give us your plan and doing steps for this.

Thank you very much

Ngoc

Hello,

Please let us know how do we check if our application has any impact on SNMP feature on the MFP.

Thank you,

We recently discovered that some customer sites were unable to register their devices when the RightFax server and devices are configured to use SSL/TLS only. During testing, we found an exception being thrown in our code that was not handled correctly. After fixing that issue, we were able to register the sdk/j application. However, at runtime, we have encountered unhandled exceptions being raised in the Java code. We configured the device to ignore certificate host errors and also installed intermediate certificates from a trusted source, but the Java runtime does not appear to recognize these as legitamite certificates. Is there any other steps we can take in our runtime code to handle these certificate errors? I'm also including the logs and wireshark trace in the hopes that you will be able to provide some insight.

Thanks very much in advance,

Dale Hunt

Software Engineer IV

Open Text