Posted on 03-04-2013 11:40 AM
I have a OS Developer account, but can't seem to sign the packages. Well, let me say that the P12 file I gave it seemed to take ok, but when I download the package it says that it's damaged and wants to trash it. So I'm not doing something right.
Does anyone have steps to get it working? I went into developer.apple.com and created a installer ceritifcate. I then installed that certifcate in my keychain and exported the P12 of that. Am I missing something?
Posted on 03-04-2013 11:49 AM
Hi Roie,
This thread on JAMF Nation from a while back has some useful links:
https://jamfnation.jamfsoftware.com/discussion.html?id=6036
Hope this helps!
Jeff
Posted on 05-12-2015 06:31 PM
Roie - did you fix this issue? I know this is an old post. But i have the same issue. Right now i just want to revert back without the cert. So i removed it, but everytime i do an enroll via url the package is damaged and wants to be trashed. any ideas how i can revert back? I already removed the cert and unchecked the box.
Posted on 05-12-2015 06:34 PM
You need to make sure you are the agent of the account to be able to request the correct cert.
Are you using user initiated enrollment or using a recon-generated quickadd?
Posted on 05-12-2015 06:51 PM
@Simmo - I am using user initiated enrollment. This issue occured after i removed the cert and made the settings how it was originally. The sign quickadd package box was checked and thats where i added the cert. I removed and want to revert back.
Now when we enroll via url i get the "QuickAdd.pkg is damaged and can't be opened" message.
Posted on 05-12-2015 07:04 PM
Seems like the certificate has gotten stuck.
I'd try disabling user initiated enrollment and re-enabling it, or try uploading a different cert in place of the one you have in there then unchecking the sign quickadd checkbox again.
Otherwise you may need to contact JAMF Support on that one.
Posted on 05-12-2015 07:19 PM
Thats what i was thinking. The cert seems to be stuck somehow. Ill go ahead and try what you suggested.
Thanks!
Posted on 05-13-2015 09:55 AM
Fixed my issue - had to restart the server itself.