Quantcast
Viewing all articles
Browse latest Browse all 2218

Plugin Signature check

I am trying to test our plugin (written in Angular/Clarity) with the new HTML client.  In the flash webclient our plugin deploys successfully.  I have the type="html" entry on the <pluginPackage> in the plugin-package.xml.   Despite that it doesn't appear in the HTML client (<IP>:9443/ui).  

When I look at the virgo log file I find the following entries:

 

[2017-09-01T20:50:44.403Z] [WARN ] vice-extension-mngr-pool-121 70000079 100038 200001 com.vmware.vise.util.PropertyUtil                                 The value of property 'plugin.signature.check.enabled' couldn't be parsed to boolean. Will use the default: true

[2017-09-01T20:50:44.410Z] [WARN ] vice-extension-mngr-pool-121 70000079 100038 200001 c.vmware.vise.vim.directory.extensions.DirectoryExtensionManager  Detected an invalid signature for plugin: com.vmware.vcIntegrity.vcIntegrity:6.5.0 com.vmware.vise.extensionfw.signing.PluginSignatureException: No META-INF/MANIFEST.MF entry found in the plugin zip file.

        at com.vmware.vise.extensionfw.signing.PluginSignatureServiceImpl.verifySignature(PluginSignatureServiceImpl.java:171)

      ......

 

Which property file should have this signature enabling/disabling. Where is the documentation on this?  If I just leave it set to true, will we be forever good or will we eventually need to add some kind of siguature to our plugin?

Image may be NSFW.
Clik here to view.

Viewing all articles
Browse latest Browse all 2218

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>