However, if you are using ScriptMaster to generate your own plugins, you will need to generate them with an unsigned version of the ScriptMaster plugin, then sign them with your own code signing certificate. So if you are strictly using ScriptMaster to register modules and execute the RegisterGroovy or the EvaluateGroovy functionalities of the plugin, you can use the store version without issues. The default store version of ScriptMaster, which you can download at this page here, comes already signed by 360Works. Whitelisting the plugin will allow it to run after you have turned Gatekeeper back on.įileMaker 18 requires that all plugins come with a signature, which indicates that the software is valid, unchanged, and made by a certain developer. Launch the plugin, this will "whitelist" it.This does pose a security risk, and if you do decide to do this, it is best if you: You can disable Gatekeeper using the instructions here: This shows how you can use the command line tools to notarize your plugins after you have made them:Īlternatively, if you want to run a plugin on Mac without notarizing it, you can disable the Mac OS Gatekeeper. This provides a good outline of Notarization: Notarization is fairly involved, and is well documented on Apple's developer pages. Mac OS Catalina (10.15 and later) have introduced a security requirement that requires all executable software to be Notarized by Apple in order to run. 6 Using Get( InstalledFMPlugins ) with custom plugins generated by ScriptMaster.5.4 When using Select File module I get spinning beach ball (Mac).
0 Comments
Leave a Reply. |