search

autopkg / nstrauss-recipes

Public AutoPkg recipes
23 stars 27 forks source link

RespondusLockDownBrowserLab.download.recipe unable to download #22

Closed MLBZ521 closed 2 years ago

MLBZ521 commented 2 years ago

Respondus moved the Lab Edition download page behind a login. So your com.github.nstrauss.download.RespondusLockDownBrowserLab recipe doesn't work anymore.

I have my own pkg recipe, which I've moved to using your standard edition download recipe (com.github.nstrauss.download.RespondusLockDownBrowser) instead and configuring the installation package to function as a Lab Edition package.

Just wanted to provide a PSA for anyone else looking at this.

nstrauss commented 2 years ago

@MLBZ521 Thanks for the heads up. I've been arguing with Respondus support for the past 10 days trying to convince them to revert the change their download URL for the lab version. I'm fairly sure they're sick of me at this point after I pointed out their additional security doesn't make the product more secure.

If you have a working version which writes the lab.txt file then please open a PR and I'll merge. I'd rather not have multiple versions floating around the autopkg community when possible. I was holding out hope Respondus would listen to reason sooner, but no such luck.

MLBZ521 commented 2 years ago

Really not surprising....given how silly it is in the first place. It's literally the same .pkg regardless which you download.

So, in my recipe, I'm not writing the id.txt and lab.txt files. Instead, I'm just renaming the downloaded .pkg the same as what Respondus' postinstall script expects and then performing "package inception" so that the Jamf Pro "package display name" is the standard, expected format and because Respondus does silly things like expecting the licensing information in the file name of the .pkg. Because of this, my recipe also does not install the LDB on the AutoPkg runner/system along with performing a few fewer steps to get the desired results.

Here's my pkg recipe. Happy to submit a PR though if you want to adopt this take on the recipe workflow.

nstrauss commented 2 years ago

Edited my recipes to copy the student package to include the lab hash and then run the install recipe. Updated the readme to include a link to your recipe as well. I really like your approach as well and think both are reasonable solutions. Excluding the install step in yours is admittedly a bit better. Going to stick with what I have for now since it's closer to the "supported" solution. Maybe one day Respondus will come to their senses.