I have a client that updated recently from 3.x which is currently supported on ESAP 1.5.9 and prior, to the more current version 4.x any idea if that will be supported in the next ESAP release?
I already posted this question from our partner Opswat and havent got a reply yet. If I hear from them soon then I will reply to this thread next week. Please open a JTAC ticket soon if you want to get this fixed in ESAP 1.5.10.
OPSWAT has already provided the SDK for 1.6.0 (ESAP 1.5.10) and it doesn't have fix. so this will have to go into the next release. We should give the customer a workaround of checking the process and let them know that OSWAT is QAing it.
the agency has left 1 machine as 3.x to allow them to connect, is there a work around that I could put in place to validate 4.x machines correctly till the release of I assume ESAP 1.6.1, as you stated ESAP1.6.0 will not correct the issue?
