You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

rdjst Author

Level 1

0 points

macOS Server (5.11.1) / Signed configuration profiles

All,

I'm seeing an issue where configuration profiles are showing up on devices as being "Unsigned" when installed via the MDM (Profile Manager). If I download the exact same profile, it says it's "Verified"...

I have the "Sign configuration profiles" checked in Server... The code signing cert is valid... I'm at a loss as to what else I can check.

Has anyone else seen this? Any ideas on how to correct?

Thank you.

Posted on Dec 2, 2021 6:21 PM

Similar questions

code signing works well - but the app shows damaged (gatekeeper spctl check fails) Hello, We are working on a project which uses code signing to sign the application. While building the app code signing works well with a valid certificate and apple developer id. But somehow the package when opened shows as damaged. We tried debugging gatekeeper spctl check by following command. spctl -a -vvv -t install MyApp.app We are able to get accepted for same package on one mac machine , but for one of the other machines we face this error for above command . MyApp.app : a sealed resource is missing or invalid We are facing this issue on macos ventura and not on bigsur. The macos version is 13.6 . Please help us understand the cause for this inconsistency . I will be appreciative for response on this thread.
256 2
Updating Certificates/CAs This article (https://support.apple.com/en-us/HT204446#:~:text=To%20update%20a%20certificate%2C%20in,certificate%20profile%2C%20then%20click%20Update.) claims "To update a certificate, in the Profiles pane of System Preferences, click the certificate profile, then click" But there is no "certificate profile" in System Preferences on Catalina. wtfo??
687 7
Importing certificates into MacOS Server Yeah, I know this is antique software. But we use it to run a shared household calendar server on an antique Mini running Sierra (the last release Server runs on), and it still works fine. Maybe a fellow antique user can help me out. I spent like six hours tonight trying to generate a formal (not self-signed) security certificate from Let's Encrypt. (The calendar server is open to the Internet because we use it while on the road.) Much time wasted because the process needed brew, brew no longer works on Sierra, etc., etc. Finally ran the certificate generation process from a more modern machine, and copied the resulting files over to the old Mini. This ---> <--- close to success, right? I can't get Server to import the private key. When I drag the "privkey1.pem" file into the box that says "Drag a file containing your private key here," I get an error dialog box saying that the contents are unrecognizable. It surely looks well-formed to me in Text Edit. Do I perhaps have a suffix issue? I see a lot of hints on the web that talk about installing files to OS Server that end in .crt and .p12 . I did notice that although Server doesn't outright reject the other three files, it bundles them in as "extra non-identity certificates" and doesn't recognize the public certificate file for what it is. As a test, I dragged all these files into Keychain Access. The cert1.pem file seemed to create a well-formed certificate, and the other two at least weren't rejected, though I'm not sure where they went, if anywhere... but the privkey1.pem file got rejected. For giggles, I exported the certificate, which created a .crt file (hm!). I tried feeding that into Server, but it stuck it under "extra non-identity certificates" again. I'm bumfuzzled, bleary-eyed, and going to bed. Appreciate any assistance.
672 1

There are no replies.

macOS Server (5.11.1) / Signed configuration profiles