GSNX

Hi,

We were told by Yann.PECHA@ricoh.fr to reach out to RiDP in regards to the following SLNX request:

Kofax are developing zero trust for Ricoh on Printix and we need to start finalizing how we can deploy and configure the embedded application (setting SP modes) on the device, we believe that SLNX maybe able to be used to deploy and configure our embedded application and need to talk to someone at Ricoh who can help us with this, can you suggest someone that we can contact about this?

Thanks.

Hi,

We are trying to test our GSNX Plugin with our version of the SOP Embedded version, but we can not push the SOP version of GSNX Device Client to the IMC2000.

Please can you advise how to push the correct package to the device?

kind regards

Clive

Sometime (randomly), when logging in into PCC5, the authentication data is no longer parsed to GSNX using the AAA API. After rebooting the device, functionality resumes.

We escalated this to RCL and they came back with the following:
The problem is that the SSO plugin sometimes doesn't transfer the users destination information towards GSNX serverless.
GSNX SSO Option has registered a listener by the AAA Client method(com.ricoh.auth.Authenticator#addListener()), but it doesn't receive any notification of authentication from AAA provider.
The log below confirms that the listener has been registered.

We did communicate with AAA team and check our app logs they suggested GSNX team to have a look that not caused by AAA Provider

Hi,

We are working with a customer to change the behavior of the interaction between Pharos and GSNX. Please see this incident in RiDP for details.

To continue with this change I need GSNX software for two MFPs, an MP C401 and an MP C3003. My goal is to make the change and test on a legacy MFP and an MFP with an SOP panel.

Can you provide GSNX software and licenses for this task? This software will not leave our lab.

We are using GSNX Serverless 2.4.1.0.

Thanks,

Nick.

Customer is requesting that when the GSNX logout button is pressed that the Pharos GSNX plug-in not capture the event and log the user off the MFP. Instead they want to return to the GSNX project screen.

We implemented the logout of the MFP workflow on purpose, I think because back when we did it, there was no way to logout of the MFP with the hard keys because the auth app had to have focus for the logout event to be captured.

Since then SDK/J and some FW (from about mid 10.x timeframe) have the ability to capture the logout event even when the auth app does not have focus. This would allow the user to logout by pressing the hard logout key (not sure how this represents itself on SOP devices) even when the auth app does not have focus and be a reasonable workflow.

My question to Ricoh is: does the reason for the workflow as described ring a bell? I think we did it this way and just want to make sure that there is no other reason. Second question is: is unchaining the logout a reasonable change to make moving forward with MFPs? 

Thanks,

Nick.

Wells Fargo has observed that switching to GSNX from the Pharos print screen isn't working on the SmartOPS panel. they have to go to Home and then go to GSNX.

Does this sound normal and expected on an SOP panel?

Thanks,

Nick.

Hi,

I would like to request acess to installation binaries and test licenses for the GlobalScan NX server for testing purposes.  Support is being added in PCC5 for launching GlobalScan NX from the PCC5 launcher. 

In order to test that the application starts correctly, Nuance requests access to the the server binaries to ensure that the GlobalScan NX Application running on the panel starts correctly and can connect to its server as expected.

Thank you.

Regards,

CRISTIAN CRACIUNOIU
Software Development Manager
Nuance Document Imaging
450 Phillip Street
Waterloo, Ontario N2L 5J2

Obtain GSNX SSO Specfication document.

Hi,

Before I start I want to say I don't have the SMC report. I have requested it but until it's provided I hope you don't mind that I gamed the system to get this ticket started. I understand the need for the information but it's a PIA to get the customer to generate a SMC report because it requires a Ricoh tech. If at any time you can convince RCL to make access to the report easier, like through the web browser, that would go a long way toward adding tickets easier. Thanks!

With that out of the way, I think this is a networking problem at the customer site but I think they went down a path where they found a procedure that "works" and made assumptions from there. It's also possible this is an issue with our network monitor thread exasperating a problem that was in Java that I think was fixed in FW. I don't recall the specifics of that.

So here's the issue:

At Apple they use 4.x and 7.x devices with Pharos and GSNX.  The report is on some MFPs they lose connectivity to Pharos and the solution is to reinstall the SSL certificate that we ship with our solution.

The questions:

1. The Pharos iMFP for Ricoh for SDK/J platforms uses a method of adding an SSL certificate to the MFP that Andy got from you. This method, as I understand it, replaces the SSL certificate for all of Java on the device and the speculation is (was) that another app that uses the same method might be replacing our certificate if it is installed after Pharos.  The only other app on the box is GSNX 2.3.1.  So, do you think it's possible that Pharos and GSNX are somehow corrupting each other's SSL certificates?

2. Do you recall an issue in the past where there was a problem in the Java platform that was exasperated by our network monitor thread? This thread opened a socket to our server over SSL the closed it immediately. This was used as a method of checking the link to the server. The use of this thread and the open/close of the socket over SSL was the issue. I think we modified our solution to open/close the socket over port 80 instead and this may have solved it. The reason for the question is: if there was a change in Java, what versions of FW for 4.x and 7.x devices was it changed?

Thanks,

Nick.

What's the most recent version of the Java SDK that can be targeted by a GSNX plugin (log type)? Does is depend on the Java version installed on the GSNX server, or does GSNX server require plugins to support a specific Java version?

For example can we use generics in our plugin development (requiring Java SE 5.0)?

Cheers,

-Larry