Open topic with navigation
Code Signing OS X–Based Installers
InstallAnywhere 2013
InstallAnywhere has support for signing OS X–based installers with a Developer ID installer certificate at build time. Signing an installer with this type of certificate enables you to distribute it outside the Mac App Store. When an end user downloads and runs your installer, Gatekeeper allows the installer to run.
If an end user tries to launch an unsigned, downloaded installer on an OS X Mountain Lion system on which Gatekeeper is turned on, the system displays an alert and blocks the installer from running.
Obtaining the Certificate and Preparing Your Build Machine to Sign OS X–Based Installers
To obtain the certificate and prepare your build machine for signing:
|
2.
|
On OS X 10.75 or later systems, sign in to the Member Center by clicking the Member Center link on the Apple Developer site. |
|
3.
|
Use the Developer Certificate Utility on the site and the Keychain Access application on the Mac system to create a certificate signing request (CSR). |
|
4.
|
Use the Developer Certificate Utility to generate a developer ID application/installer certificate. |
|
5.
|
Install the certificate on the OS X–based machine. |
|
6.
|
In Keychain Access, locate the installed certificate and export it to the PKCS #12 certificate file format (.p12). When you are prompted for the certificate password, enter it. |
Your machine is now ready for code signing your OS X–based installer from within InstallAnywhere.
If you want to be able to code sign your installer from within InstallAnywhere on a different machine than the one from which you obtained the certificate files, you need to export the certificate files from the original machine, and then import them into the machine that has InstallAnywhere. To learn how, or for more information on the process of obtaining the certificate, see Code Signing Your App in the Tools Workflow Guide for Mac in the Mac Developer Library.
Configuring Code-Signing Information in a Project
To configure code signing for your OS X–based installer:
|
1.
|
In the Advanced Designer, on the Project page, click Platforms. The Platforms view opens. |
|
2.
|
In the Mac OS X area, in the Authentication category, ensure that No is selected for the Generate Launchers for 10.4 and Earlier (Code Signing Not Supported) setting. |
|
3.
|
In the Code Signing setting, select the Code Sign the Generated Installer check box. |
|
4.
|
Specify the location and password of the certificate. The use of build-time variables for the certificate location and password is highly recommended for security purposes. |
|
a.
|
For the PKCS #12 File setting, specify the fully qualified path for your PKCS #12 file (.p12). |
|
b.
|
In the Keystore Password setting, specify the certificate’s password. |
For information on how to test your code-signed installer, see Distributing Outside the Mac App Store in the Tools Workflow Guide for Mac in the Mac Developer Library.