Skip to main content
Jamf Nation, hosted by Jamf, is a knowledgeable community of Apple-focused admins and Jamf users. Join us in person at the ninth annual Jamf Nation User Conference (JNUC) this November for three days of learning, laughter and IT love.

Customizing the Jamf Connect Login Package with Composer

Overview

This article explains how to use Composer to customize the Jamf Connect Login installer package. Customizing the Jamf Connect Login package allows you to do the following:

  • Add files to the package, such as images and scripts.
  • Change the postinstall script to support either OpenID Connect or Okta authentication.
  • Prepare Jamf Connect Login for deployment via policy or automated device enrollment.

Requirements

Customizing the Jamf Connect Login package involves the following steps:

  1. Create a package source for Jamf Connect in Composer.
  2. Add the Jamf Connect Login Package Installer to the package source.
  3. Create a postinstall script to install Jamf Connect Login.

Step 1: Creating a Package Source for Jamf Connect in Composer

You can create a package source for Jamf Connect Login by creating a folder on your computer where you want your custom files to be installed during deployment. Then, you can use the drag-and-drop method to create the new package source in Composer. Complete the following steps to create the package source for Jamf Connect Login:

  1. Open Finder.
  2. Press Command-Shift-G to prompt a search window.
  3. Enter the file path that you want to use to store your Jamf Connect custom files during deployment, and then click Go. Note: Since images are only used at the login window, storing your Jamf Connect folder at "/usr/local" is recommended.
  4. Create a new folder in the your chosen location. If creating the folder at "/usr/local" or another privileged space, you may be prompted to authenticate as an administrator to create the folder.
  5. Name the folder "jamfconnect" or something similar.
  6. Add your custom files and images to the folder.
  7. Open and authenticate to Composer, and then drag your created file from the Finder to Composer's sidebar. A new package source should appear. Note: Renaming the package with more detail, such as the app version and authentication method, is recommended.
  8. Make sure the permissions of your "jamfconnect" images folder match the permissions of the local folder, and then click the Action button to the right of the X-column, and select "Apply Permissions to jamfconnect and All Enclosed Items" in the pop-up menu.

Step 2: Adding the Jamf Connect Login Installer Package

After creating a package source for Jamf Connect, you must configure the package to install Jamf Connect Login. Complete the following to add the Jamf Connect Login installer package:

  1. Open Finder.
  2. Press Command-Shift-G to prompt a search window.
  3. Enter the file path that you want to use to store the Jamf Connect Login installer package during deployment, and then click Go. Note: Since the installer package is only needed for installation, storing your Jamf Connect Login installer package at "/private/tmp" is recommended.
  4. Drag the Jamf Connect Login installer package from the Finder to the right-side pane in Composer. The package and its file path should now appear in your Jamf Connect package source.
  5. (Optional) If you are using Okta to authenticate with Jamf Connect Login, you must change the Jamf Connect Login installer package name to include "okta". This changes the postinstall script in the package to enable Okta authentication. Capitalization and placement do not matter when adding "okta" to the package installer name.

Step 3: Creating a Postinstall Script to Install Jamf Connect Login.

To ensure Jamf Connect Login is installed, you must add a postinstall script to your package source. Complete the following to add the postinstall script:

  1. Right-hand click the Scripts folder under your Jamf Connect package source.
  2. Click Add Shell Script > postinstall. A postinstall script should appear in the Scripts folder.
  3. Delete all the default script content except the first line, and then copy and paste the following:
    installer -pkg /private/tmp/JamfConnectLogin-1.2.1.pkg -target /
    You can also add the following to immediately remove the package installer after installation:
    rm /private/tmp/JamfConnectLogin-1.2.1.pkg
    Note: Make sure the package name in your script matches your Jamf Connect Login installer package name in Composer. Your script should look similar to the following:
  4. Navigate to a different file in your package source, and then click Save when prompted.

The package is now ready to be built and deployed via Jamf Pro policy.

If you are deploying Jamf Connect Login via automated device enrollment, you must sign the package with Jamf Pro's built-in certificate authority (CA) or a certificate from Apple's developer program.

For more information about signing certificates, see the following Knowledge Base articles:

Additional Information

For additional information about Jamf Connect Login, see Jamf Connect Login in the Jamf Connect Administrator's Guide.

For additional information about using Composer, see the following sections of the Jamf Pro Administrator's Guide.

Like Comment
JAMFBadge
SOLVED Posted: by brendon.paucek

This article has been updated to include new steps for customizing the Jamf Connect Login package.

Like