Use domain-specific naming in 'PayloadDisplayName' key of configuration profiles #292

Closed
opened 2026-01-19 18:29:57 +00:00 by michael · 1 comment
Owner

Originally created by @matt-taylor934 on GitHub.

Problem to solve

When uploading configuration profiles to Jamf Pro the PayloadDislayName key is used as the display name for the configuration profile object. Currently this is set to 'macOS Baseline settings' across every single profile created and when uploading signed profiles we're unable to change this value, meaning each profile is named the same and most without a visible payload to differentiate one from another.

Currently we're required to build each profile as unsigned, edit the key then sign manually before upload.

Intended users

Jamf Pro customers.

Further details

Ease of administration and maintenance.

Proposal

Use a similar naming convention but include the preference domain for which the profile is being used to manage.

Originally created by @matt-taylor934 on GitHub. ### Problem to solve When uploading configuration profiles to Jamf Pro the PayloadDislayName key is used as the display name for the configuration profile object. Currently this is set to 'macOS <baseline> Baseline settings' across every single profile created and when uploading signed profiles we're unable to change this value, meaning each profile is named the same and most without a visible payload to differentiate one from another. Currently we're required to build each profile as unsigned, edit the key then sign manually before upload. ### Intended users Jamf Pro customers. ### Further details Ease of administration and maintenance. ### Proposal Use a similar naming convention but include the preference domain for which the profile is being used to manage.
Author
Owner

@matt-taylor934 commented on GitHub:

Can upload the preference files for each profile as App & Custom Setting payloads.

@matt-taylor934 commented on GitHub: Can upload the preference files for each profile as App & Custom Setting payloads.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: usnistgov/macos_security#292