jamf-custom-profile-schemas / profilemanifestsmirror Goto Github PK

I'm trying to set a tenant key for AllowTenantList. When I do this, the plist preview, and what hits my mac is malformed. Here is a snip of what I'm getting w/ this JSON:

<key>AllowTenantList</key>
    <dict>
      <key>{{key}}</key>
      <string>REDACTED</string>
      <key>{{value}}</key>
      <true/>
    </dict> 

What I would expect is:

<key>AllowTenantList</key>
  <array>
   <dict>
    <key>REDACTED</key>
    <true/>
   </dict>
  </array>

S00350/Sho-Hacker-#1

I just tried menu.nomad.login.ad.json and it doesn't work right. It creates a lot of default blank values that trigger unintended behavior. For example, a blank EULA text will trigger the EULA to display.

https://chromeenterprise.google/policies/#HighEfficiencyModeEnabled

https://github.com/Jamf-Custom-Profile-Schemas/ProfileManifestsMirror/blob/main/manifests/ManagedPreferencesApplications/com.microsoft.autoupdate2.json

Jamf says JSON is invalid. JSON Validator says, it's not.

I am not sure how to describe the issue other than to say I have not been able to get this to work. I am trying to set it as a config profile in my school to prevent student macbooks from airplaying. I believe I have everything set up correctly, and I entered AA:BB:CC:DD:EE:FF into both allow lists, but the test computer that has the config profile can still airplay to other devices. Can you offer any suggestions as to what might be going on?

Hello, I noticed there is no suitable .gitignore file in this repository. I can gladly raise a PR regarding this if you assign me.

Missing allowGameCenter (and related keys) from com.apple.applicationaccess-macOS.json

https://developer.apple.com/documentation/devicemanagement/restrictions

The Application ID for New Teams is:

TEAMS21

Can support for this be incorporated into the Microsoft Autoupdate schema?

https://github.com/Jamf-Custom-Profile-Schemas/ProfileManifestsMirror/blob/main/manifests/ManagedPreferencesApplications/com.microsoft.autoupdate2.json

For https://github.com/Jamf-Custom-Profile-Schemas/ProfileManifestsMirror/blob/main/manifests/ManagedPreferencesApplications/com.tinyspeck.slackmacgap.json

 "SlackDefaultSignInWorkspace": {
            "type": "string",
            "title": "Default Workspace",
            "description": "Sets the default workspace for Slack sign-ins.",
            "links": [
                {
                    "rel": "More information",
                    "href": "https://slack.com/help/articles/360041725993-Share-a-default-sign-in-file-with-members"
                }
            ],
            "property_order": 10 

What value is expected here? Should it be the "friendly" name, i.e contoso.slack.com? or the Slack Team ID, i.e T7THYRTMD?

The Nudge payload in here ie messed up. Can you add the one from the Nudge GitHub?

https://github.com/macadmins/nudge/blob/main/Schema/jamf/com.github.macadmins.Nudge.json

This is more a reminder for myself than anything else, but one scenario that I haven't checked that Jamf can deal with that profilemanifests does is whether or not both the preference, value and key can be both customized by the admin.

Is this possible and if so, how does the script currently handle this scenario?

Since the last build updates this has been failing. Haven't been able to decipher what the issue is.

FYI:

Thanks for creating the JSON manifest.

The menu.nomad.login.ad.json JSON Manifest displays invalid JSON errors in Jamf Pro but passes JSON linter validation JSONLint https://jsonlint.com. This JSON Manifest works...

https://github.com/Jamf-Custom-Profile-Schemas/ljcacioppo-schemas/blob/main/menu.nomad.login.ad.json

It appears support for the manifest key pfm_value_inverted has not been implemented, therefore manifests which make use of this to invert boolean values end up with reversed behaviour for example com.apple.preference.security.plist.

I can't see what is wrong with the XML but I will admit I am new to this. Could you please take a look at this and see if there is a way to fix it along with adding AutoLaunchProtocolsFromOrigins key if it isn't already there. Thank you.