
Gatekeeper with multiple security levels
Since Mac OS X 10.7 "Lion", Gatekeeper has three security levels with which new programs can be executed:
- Mac App Store - Only allows the installation of programs from the Mac App Store.
- Mac App Store and verified developers - Allows the installation of programs from the Mac App Store and the installation of programs with a valid code signature.
- No restrictions - Allows the installation of any programs, whereby a corresponding warning message appears at startup. This option in Gatekeeper is no longer available as of macOS 10.12 "Sierra".
Since macOS 10.12 "Sierra", software developers on the Mac platform can no longer avoid providing the application with a code signature, because otherwise the application simply cannot be installed. However, if a FileMaker Runtime solution has already been installed in an older operating system version, the FileMaker Runtime can continue to run without any problems after an update to macOS 10.12 "Sierra".
Valid certificate as Apple developer
In order to provide a FileMaker Runtime solution with a code signature, membership as an Apple developer is required, for which an annual fee of 99 euros is charged. However, there are no additional costs for corresponding certificates.
Register as an Apple developer
Once you have successfully registered as an Apple developer, the main menu for the Apple Developer Program account you have created will appear.
To create a new certificate, select the menu item "Certificates, IDs & Profiles". The example screenshot already shows three certificates that have not yet been created for you after a new registration as an Apple developer. Select the "OS X" entry in the pop-up menu above the menu bar in the left-hand column.
To create a new certificate, click on the button [+].
On the "What type of certificate do you need?" page, select the following options:
- DevelopmentMac Development, if you only want to use the certificate for test purposes.
- ProductionDeveloper ID, if you want to use the certificate for the distribution of your software.
On the "Select the certificates you want to generate" page, select
- Developer ID Application for the FileMaker Runtime solution.
- Developer ID Installer for any installation program.
On the "About Creating a Certificate Signing Request (CSR)" page, you will be asked to create a CSR file with the macOS keychain management:
- Open the keychain management in /Programs/Utilities.
- In the menu bar, select the entry [Keyring management > Certificate wizard > Request certificate of a certification authority].
- Enter the following in the [E-mail of the user] Enter your e-mail address.
- Enter the following in the [General name] your name.
- Leave the field [E-mail from the cert. authority] empty, even if the field should say "Required".
- Select under [Inquiry] the option [Save to hard disk] and click on [Continue]to create the file and save it to your hard disk.
On the "Generate your certificate" page, you will be asked to upload the file saved in the keychain management. To do this, click on the [Choose File] and select the corresponding file. Then click on the button [Continue].
On the "Your certificate is ready" page, you can now download the finished certificate to your Mac. After downloading, navigate to the downloaded key file in the Finder and double-click it to add it to the keychain management. This completes the installation of your certificate in the keychain management. Repeat the process if you want to generate your own key for a possible installation program.
Signing a FileMaker Runtime solution
Christian Schmitz from Monkeybread Software has created instructions on how to add a code signature to a FileMaker Runtime solution. Call up the Instructions in your web browser and download the "signscript.zip" file available there. Unpack the zip archive and open the file [SignScript] in a text editor such as TextWrangler or Fraise. If you open the file with TextEdit, make sure that you export the file in the correct format (UTF-8) at the end.
Now replace all with /Users/cs/Desktop paths with the path to your FileMaker Runtime solution. It is best to use the "Find and replace" function of your text editor to definitively replace all paths. Then replace the specified app name test.app with the name of the start program of your FileMaker Runtime solution. In the last step, replace the name of the specified certificate Developer ID Application: Christian Schmitz Software GmbH with the name of your certificate. Please note that you must encode special characters such as spaces accordingly. If you are unsure how to enter the path with any encoded special characters, open the "Terminal" program and drag your FileMaker Runtime solution into the Terminal window. The name of your program will now appear there, as it must be correctly coded and inserted into the "SignScript" file.
Now save the "SignScript" file and open the "Terminal" program. Hold down the mouse button and drag the "SignScript" file into the Terminal window and press the Return key to start. Any messages from an "rm" command regarding the failed deletion of files can be ignored. If messages about successful signing of the app appear, your app has been correctly provided with a code signature. Under "Verification" in the instructions, you will find two commands that you can use to test your app for correct code signing.
Create Mac Installer with the PackageMaker
In earlier versions of Xcode, Apple supplied the PackageMaker, which can be used to create installation programs for installing your own apps. This tool is no longer included in newer Xcode versions, but it can still be downloaded from the developer area of the Apple website. To do this, go to "Downloads" in your login area and click on "Show all downloads". The PackageMaker can be found in the archive "Auxiliary Tools for Xcode - Late July 2012". It is best to enter an appropriate search term in the search field at the top left.
Download the file "Auxiliary Tools for Xcode - Late July 2012" to your Mac and open the DMG image.
Double-click the "PackageMaker.app" icon to install PackageMaker on your Mac. You can then start PackageMaker as usual from your program directory. You can find out how to create an installation program for your FileMaker Runtime solution with PackageMaker in this Quick guide or in this detailed instructions.
Signing a FileMaker runtime solution on Windows
Under Windows, there are basically several ways to provide FileMaker Runtime solutions and associated installation programs with a code signature. The technical procedure for code signing under Windows is roughly identical to the procedure in macOS. In addition to registering as a developer with Microsoft, a security certificate must also be purchased for a specific runtime, with which the database solution can be signed. Due to the large number of options, we will be conducting further research on this topic and will publish the results in another article soon.
Exchange on the topic of code signing at the FileMaker Conference 2016
In the Forum of the FileMaker Magazine several developers have announced that they will discuss this current topic in more detail at the FileMaker Conference next week. The FileMaker Conference will take place in Salzburg from October 13 to 15, 2016.

Markus Schall has been developing individual databases, interfaces and business applications based on Claris FileMaker since 1994. He is a Claris partner, FMM Award winner 2011 and developer of the ERP software gFM-Business. He is also a book author and founder of the M. Schall Publishers.












Great instructions. Many thanks
In the script by Christian Schmitz there is a change that otherwise the signing fails in the last line.
# remove extended attributes, if present
xattr -cr test.app
This belongs before the signing commands
Very good instructions, thank you!
Another addition for people who are registering with Apple as developers: It is not enough to create a developer account. Certificates, Identifiers & Profiles are not yet visible. It's also not so easy to see how you can pay the 99 euros. To do this, click on "Join ... " at the bottom (I have forgotten what the text says). Then click on [Enroll] at the top right.
After purchase, it takes up to 48 hours for the paid account to be activated and for a certificate to be issued. You will then receive an e-mail. Until then, "Pending" will appear under the name. And until then, do not click on "Purchase...", which is confusingly displayed even though the purchase has already been made.