SmartSDK

Hi RiDP,

Please help to create a maintenance signature for the attached version (1.3.0.616)

This version includes fixing the bugs below:

- Ricoh UC -  Slow Login of 10 seconds - delay Autostore side

Thank you

Hello
.      Please find attached version 3.2.13 of the PaperCut MF application for a maintenance signature.

Hello,

Please find attached version 2.0.4 of the PaperCut Hive application for a maintenance signature.

The changes are described as follows:

• Fixed a bug in scan tracking 

Hello RIDP,

One of our important customers has encountered an issue where a card swipe login is not completing and the user see the screen hanging. What we observe in the logs is the following

Card data is received, we login to our server, and issue the platform login

09-30 11:31:30.391  1389  1389 I AuthWrap: send(jp.co.ricoh.isdk.sdkservice.auth.custom.ui.REQ_LOGIN)

We receive “ jp.co.ricoh.isdk.sdkservice. auth.custom.logic.SYS_REQ_EXTERNAL_AUTH” , then verify the user and respond

09-30 11:31:31.080  1389  1389 I AuthWrap: send(jp.co.ricoh.isdk.sdkservice.auth.custom.logic.RES_EXTERNAL_AUTH)

09-30 11:31:31.460  1389  1389 I AuthWrap: send(jp.co.ricoh.isdk.sdkservice.auth.custom.ui.NOTIFY_AUTH_SCREEN_DISP_STATE) dispState:false

We get AAA notification

09-30 11:31:31.781  1389  1389 I PrintixGo: Received AAA Login = true

However, it looks like we are not getting SYS_NOTIFY_AUTH_SERVICE_STATE_CHANGED registered through jp.co.ricoh.ssdk.sample.framework.auth.custom.ui.UIEventReceiver.onReceiveEvent

So, we continue to display a please wait on the top left corner, the user continues to see this.

The user also doesn’t see the Auth Button on the top right corner change from “Login” to “Logout” (See the image attached)

We also observed that we get a logout event sometime later which we didn’t trigger

Listener event through jp.co.ricoh.ssdk.sampleframework.auth.custom.ScreenState.ScreenStateListener causes this

[[5565]]32'47"416 776 09-30 11:32:48.043  1389  1389 I AuthWrap: send(jp.co.ricoh.isdk.sdkservice.auth.custom.ui.NOTIFY_AUTH_SCREEN_DISP_STATE) dispState:true

09-30 11:32:48.100  1389  1389 I AuthWrap: send(jp.co.ricoh.isdk.sdkservice.auth.custom.ui.REQ_LOGOUT)

09-30 11:32:49.076  1389  1389 I PrintixGo:LoRcvr: onReceive, trigger: LOGOUT_STARTED State: LOGOUT_OPERATING

However the screen remains frozen.

Our info level logging is limited, so we are not able to track all our calls.

Could you look at the attached logs?

Thanks,

Mohith

after ran veracode scan, a flaw was reported:

## Flaw ID: 1111
### Severity: MEDIUM
### CWE: 331 - Insufficient Entropy
### Repo: device-ricoh
### Sourcepath
com/ricoh/auth/provider/RandomDigitFactory.java#19
### Description
Standard random number generators do not provide a sufficient amount of entropy when used for security purposes. Attackers can brute force the output of pseudorandom number generators such as rand().

If this random number is used where security is a concern, such as generating a session key or session identifier, use a trusted cryptographic random number generator instead. These can be found on the Windows platform in the CryptoAPI or in an open source library such as OpenSSL. In Java, use the SecureRandom object to ensure sufficient entropy.

References: 
CWE (https://cwe.mitre.org/data/definitions/331.html)
 

RandomDigitFactory is in aaa library aaa-provider-2.1.0.jar.

Please note: we reported the same issue in incident 5474 which was submitted on 17 May 2025. The incident 5474 was closed and we could not find any answer in it, therefore submit this one.

Hi Ricoh Team

Please help to add signature for the attached version of RicohAndroid Client v6.0.0.1660

This version has fixed bugs co-existence with Ricoh UC (SOP).

Hi,

Since RIDP website is updated I can't find the link to download the SmartSDK documentation from https://ricoh-ridp.com/ website.

It used to be in this page, but not anymore.

https://ricoh-ridp.com/development-kits-platform-resources

I appreciate if you can help me with this.

Thanks.
 

We are having an issue with a device not returning tracking information. 
My first question is to ask if the devices are supported, and if so, is the device setup different for these devices?

The device is a Pro C5410S. 
- I see the device is listed in the SDK under Common Information > Overview > Model Information > 01. Model Specific Information (2024 autumn model).  However, it is NOT listed in the Ricoh MFP model reference (2025/04.) Is it supported?
 

Are there updated instructions on device setup for SOP applications?  For example, the Administrator and System settings on the device.  Has anything changed with the introduction of new devices?  Thanks.

Please indicate what is the answer to Incident ID#: 5477 (https://ricoh-ridp.com/ridp/support-system/incident/kofax-usa/1760638639/1753585335/5477), assigned to Anil.Bhomi@ricoh.ca.  The ticket currently shows as Closed with no answer from RIDP in our view.

Hello RIDP,

I am creating this incident partly because I am not able to find details of our discussion in some previous tickets and also missing another ticket related to this issue. For e.g. see this ticket https://ricoh-ridp.com/ridp/support-system/incident/1759340296/1743097693/5478 . I can see only the question, not your answer.

 Please see the Veracode issue report to understand the issue I want to discuss