CSIDE error - Signer information does not match signer information of other classes in same package

We created a java class where we pass a recarray and get back a JSON string. Using the previous IDE plugin (16.2.1.1421) all is happy. Using the new IDE plugin (16.2.1.570) we get back the error

"JavaObject_InvokeMethod exception: java.lang.SecurityException: class "com.opentext.util.RecArray"'s signer information does not match signer information of other classes in the same package".

Also all is OK running under the service so just reporting the issue.

Cheers...

Find more posts tagged with

Comments

Steven_Stacey

I get the same error with the new JAR. It won't load the ospaces either. I'm looking to use an older one now until this is resolved.

Hany Samuel

We have the jira https://jira.opentext.com/browse/OIDE-1204 to track the issue. Would you please help by adding a code snippet that help us to reproduce this issue to get to the root cause. We will try to put a solution in our next release if we get the information on time.

Thanks,

Hany Samuel

What you mean by not loading ospaces ? This is a different issue from the signature problem mentioned here. Please provide us with the details of the problem so we can solve it

Thanks

Hany

Hany Samuel

Quoted Steven Stacey on 07/18/2017 02:22 PM:

I get the same error with the new JAR. It won't load the ospaces either. I'm looking to use an older one now until this is resolved.

What you mean by not loading ospaces ? This is a different issue from the signature problem mentioned here. Please provide us with the details of the problem so we can solve it

Thanks

Hany

John Simon

CSide code snippit (I could not get ot the JIRA site of course)

Assoc        result        RecArray    fields         = RecArray.create( { "label", "inputType", "id", "validValues" } )RecArray.AddRecord( fields, { "Date of the training", "date", "trnFolderDate", Date.Now() } )result = $MYUTILS.JSONUtils.ToJson( fields )echo( result )

Also I send you the jar file if you like (but I prefer not to post it).

Cheers (and many thanks for the reply)...

Stephan_Baumann

Hi John,

I assume $MYUTILS.JsonUtils is where the Java class is hiding? And you are using JavaObject in the OScript of $MYUTILS to use java objects in your own .jar file?

Are the classes in your .jar file located in a package called com.opentext.util.* ? If that is the case, is it possible for you to use a different package name in your .jar file? The CSIDE plugin jar file has a digital signature since the last update and also contains a package com.opentext.util. Two jar files with the same package cause a security exception when one has a signature and the other has not.

Best Regards,

Stephan

BTW: is there any reason why you cannot use $WEBLL.JSONUtils.ToJSON() ?

John Simon

Stephan,

Thanks for the reply. I am not a java programmer (more like a java hack around that gets the job done) so let me know if what I am relaying is not making sense and I will try again.

Yes we have our own jar file that imports othome/ojlib/oml.jar to make use of the RecArray class. We suspect the issue is that the oml.jar is unsigned while the plugin is signed.

We went this route because we found $WEBLL.JSONUtils.ToJSON to be too slow for our needs. Granted this was back in CS10 and we have not done any testing in recent releases to see if it has improved. Would you know if improvments have been made?

Cheers...

Stephan_Baumann

Ok, the package naming conflict between the oml.jar and the CSIDE plugin jar is what the JIRA issue mentioned by Hany is about. This is currently our top priority issue and we are working on this one right now.

Unfortunately this means that you should use the previous version of the plugin to use this type of Java objects until the fix is available.

Sorry for that.

Stephan

Hany Samuel

The issue has been resolved and our next release will contain the fix. Meanwhile, you can get a working version of our coming release from our dev branch

\\styx.lab.opentext.com\latest\comp\les.ide\alpha-dev\MSWin32_64\media\main

any recent build will be good. When our next alpha release is ready we will post as usual on the news group and it can be accessed via go/cside

please give the new build a try and report how it will go.

Thanks,

Hany