mirror of
https://github.com/usnistgov/macos_security.git
synced 2026-02-03 14:03:24 +00:00
Use domain-specific naming in 'PayloadDisplayName' key of configuration profiles #292
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@matt-taylor934 commented on GitHub:
Can upload the preference files for each profile as App & Custom Setting payloads.