This repository was archived by the owner on Feb 5, 2025. It is now read-only.
Help with TCC Config Profile to give full disk access to Santa. #1429
Unanswered
dikshitkhandelwal
asked this question in
Q&A
Replies: 1 comment
|
You're welcome to wait for someone at Google to respond to this issue but the original Santa team has moved over to a new repository. If you'd like to re-open your issue/discussion at https://github.com/northpolesec/santa, we'd be happy to help you out there |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone,
I'm currently setting up Santa and deploying the TCC Configuration Profile via Jamf. I followed the example configuration provided by Apple, updating the PayloadUUID and adding our organization information. However, when I distribute this profile via Jamf, it doesn’t seem to work as expected. I've attached the configuration file for reference.
Interestingly, when I use the built-in Privacy Preferences Policy Control (PPPC) profile in Jamf and manually provide the Identifier, CodeRequirement, and set SystemPolicyAllFiles to Allow for all three components (Daemon, BundleService, and Santa), it works perfectly.
Here’s a screenshot of the working setup:
I applied the same settings for BundleService and Santa, and they work fine. However, the configuration file from the example doesn't seem to apply correctly when deployed.
Does anyone have any insights on why the example profile isn't working? Any suggestions on what might be causing the issue?
Thank you in advance!
All reactions