SDK/J

Hello

I have reported the case Kofax client is stopped by a unknown reason after xlet started in a few minutes.

We thought there is a conflict AAA client with GeniusMFP xlet on the device, then I have removed AAA listening on the Kofax client, but the issue still happens.

I captured the logs (attached) and see there is a power function it does suspend all xlet apps, after then it forces destroy all unsuspend xlet app, and then Kofax client is stopped.

It seems from a SDKJ xlet function with SDK_P_SYS__, and Kofax client is not suspend correctly.

My question:

- Is the SuspXlet notifyAll()/ destoryUnsuspendXlets from device function? or 3rd xlet app?

- How do we set Kofax app tobe suspend when a 3rd app forces SuspXlet notifyAll()?

------------------Logs-----------------

[stdout] [SDK_P_SYS__]SDK_SYS_POWER_MODE_STAT_PRE_INFO

[stdout] [SDK_P_SYS__]mode=3

[stdout] [PowerModeDomain] debug: action_Transition_trNightStopedPreAskCut_Effect.

[stdout] [PowerModeService] isStarting() : false

[stdout] [SDK_P_UTIL_] [.EnergyControl]PowerEventListener.askPowerOff():in

[stdout] [SDK_P_UTIL_] [.EnergyControl]PowerEventListener.askPowerOff():return true

[stdout] [PowerModeService] askCut() : true

[stdout] [PowerModeService] askNight() : true

[stdout] [PowerModeService] askLow() : true

[stdout] [PowerModeService] askHeaterOff() : start

[stdout] [PowerModeService] askHeaterOff() : true

[stdout] [PowerModeDomain] debug: check_Transition_trNightStopedPreAskCutNg_Guard.

[stdout] [PowerModeDomain] debug: action_Transition_trNightStopedPreAskCutOk_Effect.

[stdout] [SDK_P_SYSEV]  postAskPanelOff()=true

[stdout] [PowerModeDomain] debug: entry_State_stNightStoppingLock_Entry.

[stdout] [SDK_P_XLETM]susPend-All-Xlets is running!!

[stdout] [SDK_P_XLETM]SuspXlet notifyAll()

[stdout] [SDK_P_XLETM]destoryUnsuspendXlets - All -Xlets is running!!

[stdout] [SDK_P_XLETM] Stoping Xlet application = Kofax MFP Client

2020/01/21 17:53:23 2020-01-21 09:53:23 AM INFO [MFPClient]

### [State:INITIALIZED] -> [State:DESTROYING] ###

2020/01/21 17:53:23 2020-01-21 09:53:23 AM DEBUG [MFPClient] ENTER: MFPClient.destroyXlet

Thanks you

Ngoc

This is for Wells Fargo.  Related to

https://ricoh-ridp.com/ridp/support-system/incident/ricoh-sdc-canada/1576866912/37855315/3658

https://ricoh-ridp.com/ridp/support-system/incident/ricoh-sdc-canada/1577217750/1998138032/3661

https://ricoh-ridp.com/ridp/support-system/incident/ricoh-americas-corp-technology-center/1577213053/257032967/3627

Hoping the signed version will install successfully on a device here before releasing to customer.

Quick question: it is my understanding that we don't need to sign with the SHA/RSA sigalg/digestalg unless "enhance encryption strength" is enabled. Is this true? As per the SDK/j  Application Development Manual I think this is true, but the support matrix is a little complicated.

I'm looking for reasons that dev-signing locally doesn't work, and I noticed that demo and prod signing signs for both levels of crypto. (I'd just experiment with it, but the SignJar/jarsigner doesn't seem to like the devkey store when using SHA256withRSA options, and I didn't want to chase that down right now.)

This also doesn't explain why the same single-crypto dev-signing worked on the same devices 1-2 weeks ago, and now do not, but I'm looking for anything in the process that is of interest.

Production signing request. I have no idea why this package cannot be installed with a dev signature.

I can't get to http://signatureservices.ricohsv.com/ and I need this package prod signed for SDK/j deployment. I don't remember the status of these signing services. I haven't set the device I'm testing up for dev-signing yet so prod signing (with a follow up if we have to release today) is necessary.

The changes are to fix a compatibility issue with Ricoh's new SDK version for the US government compliance.  Other issues include rebranding from the Nuance logo and minor functional issues when transmittion scanned images and the session times out. 

Please see the attached zip and patch notes.

Hello

Please help us to create a demo signature for the attachment.

I cannot create a demo online via this ridp portal.

Thank you very much

Ngoc

You said:

[...]

To enable custom authentication on an XLET (since Xlet = SDK/J)

1. Proceed to set SP mode – SP-5-113-001 : 2 to 1: Expansion Device 1 (you probably are not using a device but the MFP needs to trigger action)
2. Reboot device after SP setting
3. After device reboot. Go to user tools – machine features – system settings – administrator tools – enhanced external charge unit management and select all buttons other than JavaTM/X

[...]

5-113-001 is actually labelled Optional Counter Type and it was set to 0. Setting it to 1 means "1:Key Card(RK3,4)".

I tried it anyway, rebooting and selecting the sample app in Ext Charge Unit Mgmt. On init the app still catches a thrown exception from the static method:

[...]

[stderr] jp.co.ricoh.dsdk.auth.LoginModuleSetException
[stderr]     at jp.co.ricoh.dsdk.auth.external.ExternalAuthManager.addExternalLoginModule(Unknown Source)
[stderr]     at ExternalAuthSampleXlet.initXlet(ExternalAuthSampleXlet.java:104)
[stderr]     at jp.co.ricoh.dsdk.osgi.service.multiXletManager.XletManager.handleRequest(Unknown Source)
[stderr]     at jp.co.ricoh.dsdk.osgi.service.multiXletManager.XletStateQueue.dispatchEvents(Unknown Source)
[stderr]     at jp.co.ricoh.dsdk.osgi.service.multiXletManager.XletStateQueue$1.run(Unknown Source)
[stderr]     at java.lang.Thread.run(Thread.java:619)

[...]

There is slightly different behaviour, though. Ther Xlet window will start if you tap it, though all it says is:

To use the following functions(s), set Key

Card

ExternalAuthSample

None of these strings are in the sample.

But, anyway, initXlet never really completed properly so who knows? Ideally I would just throw XletStateChangeException when this happens but it is demo/test code.

I am trying to get to signatureservices.ricohsv.com and it is timing out. I've confirmed that others here cannot reach this host.