Viewing/Editing Casper .mobileconfig files

When you import it into casper, are you passing the username as $USERNAME. I don't believe it'll pass happily trough a blank username field.

That's a good thought, but in this case, we have "Use Directory Authentication" checked, so we have only the "Outer Identity" field, where I'm using %AD_ComputerID% , which we've used on our previous configuration profiles successfully -- we usually see something like "eapolclient: System Mode using OD account 'CONTOSOMacADName$' ."

JAMF Support was able to explain this -- the configuration profile is signed with the JSS profile, which is why it won't convert and can't be directly read.

You can import the profile into iPhone Configuration Utility, remove the code signing, and export to view all or most of the settings. I say "all or most" because some properties aren't supported by iPCU, which tells me it's going to remove them. I haven't confirmed that it does this yet.

You can import and export from configurator. This will strip the code signing.

Configurator or the iPhone Configuration Utility? I've heard Configurator from two sources now, but I don't see a way to import/export when I'm in there. Note also this is an OS X configuration profile, so iPhone Configuration Utility, at least, strips non-iOS content.

Thanks!

The piece I was missing is that Supervision has to be "On" for that pane to show, so the screenshot really helped.

In case anyone is interested in a way to simply convert the mobileconfig file to xml, i've been using the following command thanks to @timsutton :

security cms -D -i name_of_config_file.mobileconfig

I found this on macmule: the same as the one above but including the output file for noobs like me ;)

/usr/bin/security cmd -D -i signed_profile_path -o unsigned_profile_path

This is a minor update to an old topic, addressing a typo in @dpratl 's command and piping the output through xmllint to "prettify" it for easier human readability. This dumps an .xml file in the same path as the original .mobileconfig:

security cms -D -i MyProfile.mobileconfig | xmllint --pretty 1 - > MyProfile.xml

security cms -D -i MyProfile.mobileconfig | xmllint --pretty 1 - > MyProfile.xml

Thank you for this!
I recently found that an older configuration profile retained some unwanted login window keys that shouldn't have been there, completely breaking our existing Jamf Connect configuration after Jamf Connect received an updated config profile.

This code allows me to inspect existing config profiles from Jamf Pro to rule out those artifact keys. The more you know!