Note that in order to require authentication for macOS or OS X–based installers and uninstallers, they must be code signed. If your installer and uninstaller installs files to and removes files from unrestricted locations such as the user’s home directory, authentication is not required on macOS or OS X–based target systems. When authentication is required and standard users who are not root users or administrative users with adequate privileges try to launch your installer or uninstaller, they are prompted to enter an administrator name and password in order to proceed. If you want your macOS or OS X–based installers and uninstallers to install files to and remove files from locations where write permissions are restricted for standard users, you can configure your project to require authentication. If an end user tries to launch an unsigned, downloaded installer on an OS X Mountain Lion or later (including macOS) system on which Gatekeeper is turned on, the system displays an alert and blocks the installer from running. ![]() When an end user downloads and runs your installer, Gatekeeper allows the installer to run. Signing an installer with this type of certificate enables you to distribute it outside the Mac App Store. InstallAnywhere has support for signing macOS or OS X–based installers with a Developer ID Application certificate at build time. Authentication support is available in the Premier edition of InstallAnywhere.About Authentication and Code-Signing Support for macOS or OS X–Based Installers About Authentication and Code-Signing Support for macOS or OS X–Based Installers
0 Comments
Leave a Reply. |