Hello,

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

The changes are described as follows:

• Added copy quota control functionality which controls copy jobs based on user quota
• Add admin login functionality when device is unlinked or offline
• Fixed an issue where app may crashes on certain devices during integrated scanning

Cheers

Hi RIDP,

We see that the installer servlet in our app is not protected by any authentication method. We are passing the device admin's user name and password in the auth header in the basic auth format in our install requests to the servlet. We also pass the XSS token you provided. However these are not checked before proceeding with the installation. I was able to send requests from POSTMAN successfully with wrong passwords and tokens.

For validation, we can call the webapi endpoint  /rws/system/auth/adminAuthRequest from the servlet to validate the admin credentials.

Do you suggest any other method?

I don't find anything about authentication of the request in the SDK

 file:///C:/Ricoh/SmartSdk_DevKit_R2203/SmartSdk_DevKit_R2203/doc/en/app_ml/900-04-0100.htm?null

Thanks

Hi Team,

Follow-up Question on Ticket #5559

In a previous ticket, it was suggested that we may use any JDK version compatible with our third-party libraries and supporting tools. However, we are now seeing the following issues:

Servlet: 
Reference: Smart Operation Panel > Development Guide > Servlet
The guide recommends Corretto 8 with -source/-target 1.6 for compiling.
> If we keep Java 8 for the servlet module, can we use JDK 21 for other modules (application code)?
> Would this mixed setup be compatible?

After our update, we will provide the build to Ricoh for signing via a ticket. Could you please confirm:
If the APK is compiled with Java 21, will this affect your signing process (beta sign, demo sign, maintenance sign)?

We are considering upgrading Java for Ricoh, but are facing several restrictions. Could you please advise?
1. If we raise the minimum SDK from 17 to 21, support for G2 devices will be dropped, and only G2.5/G3 devices will be supported.
2. Can we upgrade Java from 8 to 21 despite these restrictions? Specifically:
        > APK build with Java 21
        > Servlet WAR with Java 8
    Is this mixed setup recommended, or should we remain on Java 8?
3. The main reason for upgrading is that several libraries are ending Java 8 support, and newer versions require higher Java versions. For example, the current Spring version reports security issues, but the next version only supports newer Java. Customers are raising concerns about vulnerabilities, which is why we want to upgrade.

Given these constraints, would you recommend upgrading to Java 21 or staying on Java 8? What approach do you suggest?

Hi,

From the PCC, we are able to log in with a SamAccountName (if we specify the domain) and we are able to retrieve the rights of the built-in admins, but this does not work for custom admin accounts (with reduced rights, linked to a template).

We also noticed that the ‘Administrator Mode’ button remains greyed out when we are logged in with an administrator who has limited rights linked to a template.

Note from customer:

As you will se on the video I log in the device with my domain\samaccountname first and i am able to use my admin rights because in the FAR settings I use Admin built-in accounts, then at 1:30 i switch from built-in accounts to custom privileges account and then, you will see that the Administrator Mode Button is still greyed out and that I'm not able to use any custom privilege (because the device considers that i'm a user until i've click on the Admin Mode Button).

I have gone through the details, asked to try by enabling Authentication/Charge(Settings for administrator), since it is one of the key privileges usually need to enable.Even after enabling this, customer still facing issue with accessing custom privileges.

Can you please go through the attached video and documents provided, and let us know your comments on this.

Thanks,

Bindusree.

Dear Ricoh Support Team,

I am writing to report an issue observed with print jobs being processed via pull printing on the Ricoh IM C2000 device running Firmware version 8.05 (latest). Below are the details:

Issue Summary:

When printing multiple jobs after the device has been idle for some time or has been in sleep mode, the first print job experiences a delay of approximately 1 minute before processing. Subsequent jobs are processed without delay.

Steps to Reproduce:

1. Allow the device to remain idle or enter sleep mode for some time.

2. Send a print job using pull printing.

3. Observe that the first job takes around 1 minute before processing, while the next jobs are handled normally.

Logs Observed:

After the print job enters the STATE_JOB_PROCESSING state, there is a significant delay before it resumes.

Relevant log entries:

09-12 11:04:17.971 16757 16757 D CLOUDPRINTJOBS: StateUpdate state.toString():STATE_JOB_PROCESSING ... 09-12 11:05:16.229 16757 18375 I UPConnector: service:PrintStMcn:JobState[processing]

This indicates a solid delay of approximately 59 seconds between the state updates.

Additional Observations:

• The issue only affects the first job after idle or sleep mode.

• Jobs sent subsequently are processed normally without delay.

• The issue occurs during pull printing.

• No network failures or resource constraints were observed.

• Memory appears sufficient, and print files are downloaded successfully.

Device Information:

• Model: Ricoh IM C2000

• Firmware Version: 8.05 (latest)

Request for Assistance:

• Please advise under what conditions this delay might occur.

• Confirm if this behavior is expected after sleep or idle state or if it indicates an issue.

• Suggest debugging steps, settings, or additional logs that might help isolate or resolve the problem.

I can provide full logs or conduct further testing as needed.

Thank you for your support.

Hi,

I'm trying to demo signed a unsigned binary of the app from the website https://ricoh-ridp.com/signature-self-service as we always do and it fails with this error.

413 Request Entity Too Large

nginx/1.29.1

The unsigned binary is attached, I appreciate your help on this one.
 

Hello,

We would like to ask for a maintenance signature for Smartshare Android embedded solution.

• stability improvements

King regards

Anderson 

We are working with a customer and have been setup as a listener.  It was requested that we opened a ticket from the following findings:

"After talking to my engineering team this afternoon, they want VASION to submit a ticket to RIDP to change the Embedded CAC and SLNX CAC Client AAA attribute from user's mail to UPN  (Alt16digitnumber@mil)"

I have attached the pdf that they provided with their findings.  Please let me know if anything further is needed

NYP is using our application. They can install and run our application and use it to log into the printer. Manual logout works, but if they don't log out and wait for the printer to time out and log out on it's own, we get an error message. The user appears to be logged out of the printer but the SYS_RES_LOGOUT event comes back as false. But because our app thinks the logout failed it doesn't display the UI and take them back to our login screen. I've attached the machine logs for 2 printers that are experiencing the issue. In looking at the logs I found these 2 lines.
08-27 12:49:45.253 1334 1334 I SdkServ : CTA:SYS:action:jp.co.ricoh.advop.auth.INTERNAL_LOGOUT_RESULT
08-27 12:49:45.253 1334 1334 I SdkServ : CUI:MGR:handleLogoutResult result:false failReason:null

Is there a way we can find out why the logout failed? What could potentially prevent he logout from occurring?

I want check the info of sdk for model IMC8000,Pro8300S and Pro8210S

the old isssus was created at How to detemine which firmware support dalp preconfiguration? | Ricoh Developer Program (RiDP) 

it releated to Pro8300S , not readable file dalp becase the fireware is old less than 2.4 smartsdk

1 .Does have upgrade fimware for this model , and Have issues with other model IMC8000, Pro8210S as Pro8300S  ? 

2. Pro8210S is java platform , how to check support reading config dalp file ?

Please give me info . Thank you