MID Server tries to download signatures for synced file attachments when code signing is disabled - Known Error

MID Server tries to download signatures for synced file attachments when code signing is disabled Description During file sync when code signing is off, the MID still attempts to fetch the attachment's signature along with the attachment. When the record signature does not exist, an error message beginning with "Unable to find the signature with the sys id" will appear in the Glide system logs.

If code signing is not enabled, MID should not attempt to download signatures for synced file attachments.

General information can be seen in KB1646201 MID Server and Code Signing - Unable to find the signature / Cannot just-in-time load the signature record / Failed to verify signature

Steps to Reproduce

Ensure code signing is not enabled on the Glide instance Ensure that there is an attachment record that is downloaded by MID file sync but does not have a signature record in the sn_kmf_record_signature table (for example, a MIB, Export Set attachment, etc.) Start the MID Notice an error message like the following in the Glide system logs: Unable to find the signature with the sys id, 9420038adb903fc04a1c303f9d9619d1, for the table, ecc_agent_mib .: com.glide.codesigning.exception.CodeSigningException: Cannot just-in-time load the signature record : for documentId: 9420038adb903fc04a1c303f9d9619d1: com.glide.codesigning.output.CodeSigningOutputUtility. getCodeSigningRecord (CodeSigningOutputUtility.java:331) com.glide.codesigning.output.CodeSigningOutputUtility.getCodeSigningRecordGRUsingFields(CodeSigningOutputUtility.java:152) com.glide.codesigning.output.CodeSigningOutputUtility.getCodeSigningSignatureRecordForRestEndPoint(CodeSigningOutputUtility.java:88) com.snc.core_automation.security.validation.application.SignatureUtil.loadSignatureRecord(SignatureUtil.java:115) com.snc.core_automation.security.validation.application.SignatureUtil.getSignatureV2AsMap(SignatureUtil.java:80) com.snc.core_automation.security.validation.application.SignatureUtil.getVersionedSignatureAsJSON(SignatureUtil.java:136) com.snc.core_automation.security.validation.application.SignatureUtilJS.jsFunction_getVersionedSignature(SignatureUtilJS.java:53) java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.base/java.lang.reflect.Method.invoke(Method.java:569) org.mozilla.javascript.MemberBox.invoke(MemberBox.java:236) org.mozilla.javascript.FunctionObject.doInvoke(FunctionObject.java:674) org.mozilla.javascript.FunctionObject.call(FunctionObject.java:603) org.mozilla.javascript.ScriptRuntime.doCall(ScriptRuntime.java:2988) org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1928) org.mozilla.javascript.Interpreter.interpret(Interpreter.java:1112) org.mozilla.javascript.InterpretedFunction.lambda$call$0(InterpretedFunction.java:161) com.glide.caller.gen.sys_web_service_6c94a96683201000dada83ec37d929c8_script.call(Unknown Source) com.glide.script.ScriptCaller.call(ScriptCaller.java:22) org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160) org.mozilla.javascript.ScriptRuntime.doCall2(ScriptRuntime.java:3089) org.mozilla.javascript.ScriptRuntime.doCall(ScriptRuntime.java:2998) org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1928) org.mozilla.javascript.Interpreter.interpret(Interpreter.java:1112) org.mozilla.javascript.InterpretedFunction.lambda$call$0(InterpretedFunction.java:161) com.glide.caller.gen.sys_web_service_6c94a96683201000dada83ec37d929c8_script.call(Unknown Source) com.glide.script.ScriptCaller.call(ScriptCaller.java:22) org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160) org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:719) org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:4412) org.mozilla.javascript.InterpretedFunction.exec(InterpretedFunction.java:174) com.glide.script.ScriptCompiler.executeAndPublishMetric(ScriptCompiler.java:77) com.glide.script.ScriptEvaluator.execute(ScriptEvaluator.java:439) com.glide.script.ScriptEvaluator.evaluate(ScriptEvaluator.java:219) com.glide.script.fencing.GlideScopedEvaluator.evaluateScript(GlideScopedEvaluator.java:376) com.glide.script.fencing.GlideScopedEvaluator.evaluateScript(GlideScopedEvaluator.java:205) com.glide.processors.soap.SOAPCustomProcessor.execute(SOAPCustomProcessor.java:110) com.glide.processors.soap.SOAPCustomProcessor.process(SOAPCustomProcessor.java:71) com.glide.processors.soap.SOAPProcessorThread.processCustomWebService(SOAPProcessorThread.java:218) com.glide.processors.soap.SOAPProcessorThread.processBody(SOAPProcessorThread.java:204) com.glide.processors.soap.SOAPProcessorThread.processRequest(SOAPProcessorThread.java:176) com.glide.processors.soap.SOAPProcessorThread.run0(SOAPProcessorThread.java:131) com.glide.util.ParentedThread.run(ParentedThread.java:51)

Expected Behaviour:

Given that code signing is not enabled in the instance, there is no need for the MID Server to fetch the signature, and so no error should be shown if there isn't one.

Only if Code Signing is enabled, and a required KMF Signature record is missing for the attachment being downloaded, would an Error need logging to indicate that the feature will be broken by that fact.

Actual behaviour:

The MID Server always tries to fetch a signature, causing the error, which in turn causes a misleading MID Server Issues record .

Workaround This problem has been fixed. If an upgrade is possible, please refer to the Fixed In section to determine the latest version with a permanent fix that the instance can be upgraded to.

These errors and MID Server issues records can be ignored. There is no workaround, other than to turn off Code Signing in the instance.