Composer not including activation key

[tytran]

Recently acquired some new software called Rave Mobile Safety. I have a .pkg that I've made through composer.  It installs the software but it doesn't include the activation key.  When a user launches the software it asks them for the activation key.  Am I missing it somewhere during the process in composer or is it possible to create a script to add the key after in gets installed?

[obi-k]

The activation license is probably located elsewhere, unless the vendor supports a mass deployment solution. Many vendors leave it up to the admins, but not sure about Rave.

You could use Composer to create a "New snapshot" and then install this software on a new Mac, including the license activation. You'll see where the license file is placed and can go from there.

[sdagley]

@tytran You can definitely create a postinstall script to add the key as part of your .pkg, but in general using Composer's "Watch what happens when I install something..." mode to create a .pkg isn't really a good idea for things that install license keys because by default .pkg installers aren't going to handle installing things properly if the user account on the target Macs isn't identical to the user account on the source Mac.

I would strongly suggest you contact the vendor for Rave Mobile Safety and see if they have any documentation on deploying the software via an MDM like Jamf Pro.

If they don't you'll find https://scriptingosx.com/packaging-for-apple-administrators/ a useful guide to creating Mac installer packages.

[PaulHazelden]

Most likely place that the Key was put would be in the account you were usings Library. A pkg will put it there when you install it, but that location is not available to all users.
If you find where it was put in the User Library, you can try making a copy of the Key and put that in the main Library folder in the exact same location. Lots of these will hide in the Application Support folder. Run a test mac with the Key in this new location and see if that allows it to work for other users.

Another method I have found with this sort of thing is to activate the root account, and log in as that in the GUI and then install the app. this can sometimes allow all users to access the app. I have a couple of Apps where this is the actual given method of installing it for a multi user device.

But the advice to go back to the vendor is good advice, they may well have a solution.