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.

Scope of Self Service Plug-ins

Overview

Note: As of Jamf Pro 10.0.0 (formerly Casper Suite), support for Self Service Plug-in Bundles has been removed and “Self Service URL Plug-ins” has been renamed to “Self Service Bookmarks”. You can now use the Jamf Pro web app to configure the scope of Self Service bookmarks.

By default, Self Service plug-ins are available on all managed computers and to all users. This article explains how to distribute a Self Service plug-in using a policy so that you can control which users have access to the plug-in.

Versions Affected

Jamf Pro 9.101 and earlier

Procedure

To distribute a Self Service plug-in bundle using a policy:

  1. Create your Self Service Plug-in bundle. This file must be a .bundle file.
  2. If you want to base the scope of the plug-in on computers, place it in the following location: /Library/Application Support/JAMF/Self Service/Plug-ins/ If you are want to base the scope of the plug-in on users, place it in the following location: /Users/username/Library/Application Support/JAMF/Self Service/Plug-ins
  3. Package the Self Service Plug-in bundle using Composer or a third-party package building tool.
  4. Use the JSS to create a policy to distribute the package you created in step 3. If you want to base the scope of the plug-in on users, you must select the Fill Existing Users option.

To distribute a URL plug-in using a policy:

  1. Use a test JSS to create a URL plug-in. On computers that are managed by your test JSS, the PLIST file for the URL plug-in is distributed to the following location: /Library/Application Support/JAMF/Self Service/Plug-ins/ Note: If you are distributing more than one URL plug-in, you must verify that they each have a unique key ID. To view the key ID in the PLIST file for a URL plug-in, open the file and locate the <key>id</key><string>1</string> string.
  2. If you are scoping the plug-in to users, move the PLIST file for the URL plug-in to the following location: /Users/username/Library/Application Support/JAMF/Self Service/Plug-ins
  3. Package the PLIST file for the URL plug-in using Composer or a third-party package building tool.
  4. Use the production JSS to create a policy to distribute the package you created in step 3. If you want to base the scope of the plug-in on users, you must select the Fill Existing Users option.
Like Comment
Order by:
SOLVED Posted: by davidhiggs

New Computer location:

/Library/Application Support/JAMF/Self Service/Managed Plug-ins/

New User location:

/Users/username/Library/Application Support/JAMF/Self Service/Managed Plug-ins/
Like
SOLVED Posted: by donmontalvo

Deploying the plist to /Library/Application Support/JAMF/Self Service/Managed Plug-ins/ doesn't seem to stick, new plist files get removed eventually.

Deplying the plist to /Users/username/Library/Application Support/JAMF/Self Service/Managed Plug-ins/ works fine.

Like
SOLVED Posted: by bentoms

@donmontalvo why not scope via the JSS?

Doable since v10.

Like
SOLVED Posted: by donmontalvo

We’ll be at version 10 in a few weeks. Until then we needed a quick/supported way to scope two new ones.

Like

Jamf would like feedback on User Enrollment and General Settings within your Pro instance!