Customizing the Jamf Connect Package Installer
To prepare Jamf Connect for deployment via a PreStage Enrollment package, you may need to modify the Jamf Connect Login package before uploading it to Jamf Pro. Consider the following scenarios:
If using Jamf Pro 10.18.0 or earlier, you may want to modify the Jamf Connect Login package to do the following:
-
Include custom branding images and files read by Jamf Connect Login preferences.
-
Modify the postinstall script to execute authchanger commands that add additional features to Jamf Connect Login, such as the Notify screen, an end user license agreement (EULA), or a script.
For more information, see Additional Login Settings in the Jamf Connect Administrator's Guide. -
Rename the package to to include "okta", which automatically will enable Okta authentication.
If you are using Jamf Pro 10.19.0 or later, you may want to modify the Jamf Connect Login package to do the following:
-
Modify the postinstall script to execute authchanger commands that add additional features to Jamf Connect Login, such as the Notify screen, an end user license agreement (EULA), or a script.
For more information, see Additional Login Settings in the Jamf Connect Administrator's Guide. -
Rename the package to to include "okta", which automatically will enable Okta authentication.
Notes:
-
In Jamf Pro 10.19.0 or later, you can distribute multiple packages to computers during enrollment using the Enrollment Packages payload. Using a separate package to deploy any Jamf Connect-related branding images or files is recommended. Packages with higher priority install first. Multiple packages with the same priority install in alphabetical order based on the package name.
-
If you customize the contents of the package, you must sign the package with Jamf Pro's built-in certificate authority (CA) or a certificate from Apple's developer program.
Related Information
For more information about signing certificates, see the following Knowledge Base articles: