Edit .plist for during application deployment through JAMF

are you deploying it with JAMF? you can create a script to run after the package in a policy

echo "<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0"> <dict> <key>ShowAuthPopup</key>
 <string>0</string> <key>APIServer</key> <string>api-vip.elastica.net</string>
 <key>ENSServer</key> <string>ens.elastica.net:443</string>" >> /Library/Application Support/ReachAgent/ReachAgent.app/Contents/Resources/RANDOMNAME.plist

Im deploying the application with Jamf. When the application gets installed it creates a .plist file here "/Library/Application Support/ReachAgent/ReachAgent.app/Contents/Resources/ReachAgentConfig.plist"

I want to rewrite this .plist file to resemble:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ShowAuthPopup</key> <string>0</string> <key>APIServer</key> <string>api-vip.elastica.net</string> <key>ENSServer</key> <string>ens.elastica.net:443</string> <key>Gateway</key> <string>gw.elastica.net</string> <key>UIServer</key> <string>app.elastica.net</string>
</dict>
</plist>

once .plist has been changed I also want it to launch.

You might want to see if defaults write commands would do what you're after here. If you can post a copy of the plist as it is right after the application gets installed, we might be able to help come up with some defaults commands that can write the correct values in.
It's also possible that defaults won't work, because it doesn't always work, especially with more complex plist files. Though I suspect in this case it should work just fine. This is what your example plist above looks like when its read by defaults

{
    APIServer = "api-vip.elastica.net";
    ENSServer = "ens.elastica.net:443";
    Gateway = "gw.elastica.net";
    ShowAuthPopup = 0;
    UIServer = "app.elastica.net";
}

That seems like a very straight forward plist, so I don't see why you couldn't just use defaults commands to edit the plist.

BTW, are you sure the value for the ShowAuthPopup key is a string as you have it? It almost seems like it should be a boolean value (true/false), but I don't know since I have no experience with the Symantec Cloudsoc Reach agent.

In the documentation for Symantec Cloudsoc Reach agent it state the value should be 0

OK, cool, just checking. It's slightly abnormal, but every vendor does things their own way. As long as it works!

i'm not to sure how to to use default writes to modify this

Can you copy/paste the contents of the unedited plist file that gets installed with the application? I'm willing to bet making the changes to it with defaults will be pretty easy, but I'd need to see what the "default" plist looks like first.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict> <key>APIServer</key> <string>api-vip.elastica.net</string> <key>ENSServer</key> <string>ens.elastica.net:443</string> <key>Gateway</key> <string>gw.elastica.net</string> <key>UIServer</key> <string>app.elastica.net</string>
</dict>
</plist>

Ok, thanks. That plist file looks like this when read in by defaults

{
    APIServer = "api-vip.elastica.net";
    ENSServer = "ens.elastica.net:443";
    Gateway = "gw.elastica.net";
    UIServer = "app.elastica.net";
}

It looks to me like the only change to the file that would need to be made is:

defaults write /Library/Application Support/ReachAgent/ReachAgent.app/Contents/Resources/ReachAgentConfig.plist ShowAuthPopup 0

This would just add that ShowAuthPopup value into the file. Everything else is the same it looks like, so no other changes.

Hope that helps.

so i created a script to run this command post installation via Jamf and it didnt make the change. When i try and run it manually i'm getting the following error:

"Could not write domain /Library/Application Support/ReachAgent/ReachAgent.app/Contents/Resources/ReachAgentConfig.plist; exiting"

Might need to quote the full path to the plist to protect it, although the backslashes included in my post above should have taken care of the spaces. You added the defaults line just like I wrote it above? Either way, you could do this to see if it works.

/usr/bin/defaults write "/Library/Application Support/ReachAgent.app/Contents/Resources/ReachAgentConfig.plist" ShowAuthPopup 0

And you're certain that's the correct path to the plist file, right? Because you will get a similar error to that if the file it's trying to write to doesn't exist.

#!/bin/sh

USERNAME="$3" 
PLIST="/Library/Application Support/ReachAgent/ReachAgent.app/Contents/Resources/ReachAgentConfig.plist"

defaults write "$PLIST" ShowAuthPopup 0

That's the script that i'm using

@kaysp3cial Ok, so, if you quote a path that contains a space, you have to drop the backslashes. The backslashes are only needed for an unquoted path that contains spaces. Including backslashes and quotes together is sure to fail, because the shell will interpret the backslash as being a literal character, which of course doesn't exist in that path.
So either do it just like I originally posted it (no quotes, with backslash), or how I posted it above (with quotes, no backslash) earlier today. Not how you have it in your post 2 above this one.

I did quite a bit of research on this and talked to several people. Here's what I came up with

On a clean system.... before installing Reach.... I will create a script on Jamf to deploy before the package is installed. The script will run the following commands.

#!/bin/bash
USERNAME="$3"

mkdir -p /Library/Application Support/ReachAgent/ReachAgent.app/Contents/Resources/

After the folder has been created, I copy the ReachAgentConfig.plist in there and then do the Reach install.

Contents of ReachAgentConfig.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>ShowAuthPopup</key>
        <string>0</string>
        <key>APIServer</key>
        <string>api-vip.elastica.net</string>
        <key>ENSServer</key>
        <string>ens.elastica.net:443</string>
        <key>Gateway</key>
        <string>gw.elastica.net</string>
        <key>UIServer</key>
        <string>app.elastica.net</string>
</dict>
</plist>

I reached out to our Symantec Rep and they confirmed that the new install of Reach will preserve the Keys that were set in the existing ReachAgentConfig.plist at that location.

Please note, I was also notified that the defaults command would not work in this case. Our Customers will require to manually copy the ReachAgentConfig.plist with the required Keys.

My only blocker is how I can edit the plist file in the script without using the "Defualt writes" command?

@kaysp3cial Who informed you that the defaults command would not work, and why? Did they offer any explanation on that?

Symnantec rep informed not to use the default command, im still waiting for an update as to why

I'd be very curious to hear the explanation, since I don't see a reason why a defaults command couldn't write a value into that plist. From what you posted, it seems like a simple straight forward plist to me. The only thing I can think of is that a defaults command might mess up some privileges on the plist, but that can always be corrected in the same script if needed.