SDK/J

Hello,
 

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

- Fixed an issue where Integrated Scanning failed to start because compression was disabled.

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.

Thanks,
Austin

• Does any versions of SDK/J support TLSv1.2?
  • If so, What versions?
  • Is it device specific?
  • Is it possible to upgrade all devices to a supported version?
• If not, is TLSv1.1 supported in any way?

Hi,

I have a few questions regarding TLS support for the SDK/J platform...

• Does any versions of SDK/J support TLSv1.2?
  • If so
    • What versions?
    • Is it device specific?
    • Is it possible to upgrade all devices to a supported version?
  • If not, is TLSv1.1 supported in any way?

Hi,

Our iMFP solution, the SDK/J solution, receives a list of print jobs from a server in an XML blob. When the names are displayed on the UI (in our app) they are all boxes, not Chinese glyphs. The UI of the MFP is in Chinese so we know the MFP itself supports Chinese but we're unsure if Java has the appropriate resources to draw the Chinese characters. Attached are screen shots of the MFP's FW versions which also show the models.

Should an SDK/J app be able to show Chinese characters?

Thanks,

Nick.

Hi,

We had a previous signing request for SafeCom Go Ricoh in incident 3528. Unfortunately, it seems the signed binaries were of a previous SafeCom Go Ricoh version, *06.10, while the recent request was for version *06.19.

Can you please provide a maintenance signature for the servlet and xlet of version *06.19? Attaching the unsigned binaries and the release notes for this version.

Thank you in advance!

Sebestyen

We have 3-4 apps in the list at /forms/signatureservices/sdkj-development-keys. I'm finding that the resulting xlet-key and/or Machine-SerialCode for 34089989 and 34089987 are not working anymore. I'm not sure what has changed, but I get a J201 error when trying to install via WIM against a C4502.

Here's what I do:

- Regenerate with 34089989 selected, with a single Armada Machine ID of "W512L301111"

- Select 34089989 and download

This gets me a zip with a manifest with a single Machine-SerialCode and Xlet-Key:

[...]

Manifest-Version: 1.0
Xlet-Key: f765aa00a0b77faaff1e41956c5e9e0ce0f30433cb226acaec2b5043222a504a1524128a81f03e35eacf47a25d1c8f740ca91dfaf22416b37c3f95fe268f8d96cb848981c9d605cd680841382d686be21c0d54d447760014e1e686afc25b64a887f98c5b38f111c935e50b3336088c1da2d921f6100ea48e
Machine-SerialCode1: adde650003df9b978b19bd06e967d206f160aa7d711382f6699ae4fbe15a59e97d20bea37fc4b4caa5f36f73581795e5e183

[...]

Building using this manifest will fail with a J201 error in WIM. This used to work, so I'm puzzled about what changed. StreamLine was installed to this Armada device once upon a time. I can't imagine that would impact the Machine-SerialCode, but...?

The changes to the client Xlet includes a call to the server to do a lookup on the server's LDAP to determine the logged-in user's network groups - which are then used to limit the forms seen by the user to only those they're allowed to see.

Hi,

We would like to request a maintenance signature for the attached SafeCom Go Ricoh build (our previous certification completed in August 2019). This build implements fixes a problem affecting support for the new IM series of devices, enabling post-tracking to work.

Release notes are included in the ZIP file.

Please let me know if you have questions.

Thank you,

Sebestyen