RXOP

Hello

Our Registration tool is using XROP lib 3.6.1 to register Kofax Ricoh Android client on to SOP G2 devices.

We have a problem that the XROP lib (rxcommon.jar) is using those libraries for communication with Ricoh MFP device

- commons-httpclient-3.1.jar and commons-codec-1.3.jar

Those libs are too old, the WhiteSource has reported to us about security issues when using them. Both Ricoh and Kofax don't want to explain every customers that why those libs are there.

We are removing/upgrading all 3rd libs that they are reported by Whitesource, includes 2 libs above.

Can XROP team upgarde RXOP to newer, and what time for the next estimate release ? (ex: httpcore 4.4.10.jar and commons-codec-1.11.jar).

Else, could you pleaes have a suggestion for this problem?

Thank you very much

Ngoc

Hi there,

I'm in the middle of investigating using the RXOP libraries for our application and I noticed I need to request an ACL for certain SP settings to use with the RXSP module. I need permissions for the following SP modes:

• SP-5-401-103 (ACCESS_CONTROL__DEFAULT_DOCUMENT_ACL)
• SP-5-113
• SP-5-191

I need read/write access for all modes listed.

Hello

Our Registration Tool is using XROP 3.6 lib  to register Kofax Ricoh Android client to SOP devices.

We get an error when we register the app to a lab machine C306Z via https, althought using http protocol can work, and It can register to another devices (C2004) succesfull via https or http.

Ricoh TS local has been upgraded the lastest firmware,  but this issue is not resolved.

The attached includes: screenshot of error; Rlog data when registering the app;  The Registration Tool.

Could you please help to troubleshot the problem, and how do we resolve this issue?

C306 firmware:

Application Version

Application Name Version Part Number (or Product ID) Status M2a_System 1.27.2 D2411425F - M2a_BLEPlugin 2.12.00 D2411466 Not activated M2a_BluetoothSe 1.02 D2411465C Not activated M2a_cspf 2.02.00 D1961430B Not activated M2a_HelpService 1.00 D2411471 Not activated M2a_ICCdDisptch 2.12.05 D2411450B Not activated M2a_IDCardCopy 1.01 D1961447A Not activated M2a_iWnn 2.3.3 D1961403 Not activated M2a_iWnn_Hang 1.0.0 D1961406 Not activated M2a_iWnn_Hans 1.0.0 D1961404 Not activated M2a_iWnn_Hant 1.0.0 D1961405 Not activated M2a_LegacyUI 1.21 D2411427Y Not activated M2a_NFCPlugin 2.12.00 D2411452 Not activated M2a_ProgramInfo 1.18 D2411438D Not activated M2a_QRCode_SDC 2.1.2 D2411453F Not activated M2a_QuickCdAuth 2.12.04 D2411468A Not activated M2a_ScanToME 1.02 D1961412B Not activated M2a_ScnFldrHlpr 1.1.2 D1961448B Not activated M2a_SimpleCopy 1.20 D2411443S Not activated M2a_SimpleFAX 1.15 D2411445Q Not activated M2a_SimpleScan 1.15 D2411444R Not activated M2a_USBCdPlugin 2.12.00 D2411459 Not activated M2a_WEcoInfo 1.06 D2411437F Not activated M2a_WFaxInfo 1.03 D2411435E Not activated M2a_WLanguage 1.09 D2411431J Not activated M2a_WStopKey 1.01 D2411436B Not activated M2a_WTonner 1.05 D2411434G Not activated M2a_zoo 1.05.02 D2411467K Not activated M_1679830528 3.1 1679830528 - M_1679879168 3.0 1679879168 Not activated M_1711276120 5.0.0.944 1711276120 -

Thank you so much

Ngoc

Hello

Our Registration Tool is using RXOP 3.6 lib to register KofaxRicoh Android client to Ricoh MFP devices.

The code to bring up the app icon on the home screen: 

conf.setHomeScreenIconSetting(iconApplicationID, Boolean.TRUE, device.getUsername(),device.getUserPassword());

If devices uses Windows Authentication mode, the RXOP registered SmartSDK app success, but its icon is NOT shown on the device home screen, it returns exception error "java.io.IOException: 401:null:null"

I tried to enable 2 modes following and saw the app icon is shown on the home screen as expected (attached)

Administrator Authentication Management>User Administrator Authentication = ON

Administrator Authentication Management>Machine Administrator Authentication = ON

Could you please confirm the workaround in the case Windows Authentication mode above or not?

We will document this workaround.

Thank you so much

Ngoc

Hello,

When I have configured the WIM language to be Spanish on our MP C2004 device, when I invoke `ricoh.rxop.rxconf.Configurator.getAdminAuthSettings(...)` it throws an IOException with the message "Authentication failed". I have attached the stack trace. Looking at the source code for RXOP and I can see in the `ricoh.rxop.rxconf.AdminAuthSettings` class it gets the admin authentication settings page and does some HTML scraping. The URL it uses to get the admin authentication page is `/web/entry/en/websys/config/getAdminAuthenticationManager.cgi`. Note the hardcoded "en" locale in the URL. When the device is in Spanish and I try and open this URL in the browser it returns an empty HTML page. If the URL has the "es" locale in it instead then it works fine.

Is it a known limitation that RXOP will not work with devices set to languages that will not serve up the English version of the webpages or is it a bug? Apart from changing the device language, are there any other workarounds?

Thanks,
Daniel

Hi,

I'd like to please request support in resetting our 306/406 devices to a good state when RXOP calls start failing.  We have two 306 devices and one 406 device that have entered a bad state.  In this state, the devices usually experience some or all of these issues:

- sometimes devices don't respond to requests to obtain machine logs,
- RXOP calls to obtain the list of installed applications fail
- randomply fail to comply with requests to set some SP modes

Repeated reboots of the MFP's do not fix the issues.

This issue seems to happening with these older devices and we are unable to purchase replacement devices, but still need these devices for testing.

I would like to ask if you have a procedure for getting our test devices back to a usable state so that we can use them for ongoing PCC testing.

Thank you.

Regards,

Cristian

Hello,

We developed a deployer for our XMediusFAX application that uses RXOP to install the application on the MFP. When installing, a home screen icon is also created using the Configurator.setHomeScreenIconSetting() function. This used to work fine on the MP 305+ that we use for testing.

Recently, we reinstalled the application on the same MFP and noticed that the creation of the home screen icon fails every time. Nothing has changed in the code of the deployer (in fact, we used the exact same version of the deployer that was working previously).

The error message I get from the exception is "Connection refused: connect". 

Other than failing to create the icon, the application installs correctly.

Between the most recent tests and when it was last working I can see two things that possibly might have affected the behavior of the MFP:

- We made an upgrade of the java platform (to version 12.59.01) in order to do some tests with TLS 1.2

- We installed the SDK/J version of our application, which has the exact same name ("XMediusFAX"). I suspected that this was maybe the cause of the issue initially, but even after uninstalling the SDK/J application, I still have the same error.

Could one of the above actions be the cause of the error? If not, is there a log I can retrieve from the MFP that could give me some more info on why this is failing?

The MFP we are testing on:

MP305+

M2a_System firmware version: 1.24.1

Java platform version: 12.59.01

RXOP version used in deployer: 3.6.0

Thanks,

Peter

Hello,

We have a customer (Schlumberger) that is having an issue deploying our solution to an MPC3004 device.  I am attaching the RXOP debug deployment log, our deployment log and the SMC report.

Let me know if you need anything else.

Thanks,

 Bryan

I am looking to obtain an ACL to set the function priority setting. I attached the ACL request file.

Regards,
Mike

Hi,

We would like to request an ACL file so we can set up all configuration needed by our application remotely. Please, provide an ACL request template with all currently existent models.

We relate in the incident all required setup so you can aid us which are each one of them and what is the possible values:

• SP-5-113-001
• SP-5-113-002
• SP-5-401-230
• SP-5-401-103
• SP-5-490-001
• Enable admin management
• Enable user management and set to custom auth
• Set machine action when limit reached
• Enable track permission
• Enable stop print permission
• Set the timers (any of them)
• Auto delete user in the address book
• Notify unsupported USB device
• Display IP address

Best regards,

Fabiano