jamf / JamfMigrator

A tool to migrate data granularly between Jamf Pro servers
MIT License
140 stars 10 forks source link

Permissions #54

Closed master-vodawagner closed 4 years ago

master-vodawagner commented 4 years ago

"The source server requires an account with read only permissions on all objects where the destination server requires an account with create/read/update/delete on all objects."

Seems very excessive permissions to give. Is there nothing that can be done to give granular control?

BIG-RAT commented 4 years ago

Believe you can remove all permissions to the following:

Advanced Volume Purchasing Content Searches AirPlay Permissions Allowed File Extensions API Integrations Attachment Assignments Automated Device Enrollment Classes Computer Enrollment Invitations Computer PreStage Enrollments Device Name Patterns Enrollment Customizations Enrollment Profiles External Patch Sources File Attachments GSX Connection Keystores iBeacons Infrastructure Manager Instances Inventory Preload Records Invitations JSON Web Token Configurations Keystores Maintenance Pages Managed Preference Profiles Mobile Device Enrollment Invitations Mobile Device PreStage Enrollments Network Integration Peripheral Types PreStages Provisioning Profiles Push Certificates Removable MAC Addresses Restricted Software Records Self Service Branding Configurations


From: master-vodawagner notifications@github.com Sent: Monday, June 8, 2020 7:58 AM To: jamf/JamfMigrator Cc: Subscribed Subject: [jamf/JamfMigrator] Permissions (#54)

"The source server requires an account with read only permissions on all objects where the destination server requires an account with create/read/update/delete on all objects."

Seems very excessive permissions to give. Is there nothing that can be done to give granular control?

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/jamf/JamfMigrator/issues/54, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJYQF5JKYU5KQ4RSDYNMH3RVTG7ZANCNFSM4NYKYF7A.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/jamf/JamfMigrator/issues/54", "url": "https://github.com/jamf/JamfMigrator/issues/54", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

master-vodawagner commented 4 years ago

So looks like I need to grant full permissions to the Buildings category and then I can granular control the other permissions

BIG-RAT commented 4 years ago

?Source should be good with only read, destination read plus what ever permissions are needed to perform the desired actions. Hope that makes sense.


From: master-vodawagner notifications@github.com Sent: Monday, June 8, 2020 11:22 AM To: jamf/JamfMigrator Cc: Leslie N. Helou; Comment Subject: Re: [jamf/JamfMigrator] Permissions (#54)

So looks like I need to grant full permissions to the Buildings category and then I can granular control the other permissions

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/jamf/JamfMigrator/issues/54#issuecomment-640698112, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJYQF2I4242IDZQP6VZFDLRVT62PANCNFSM4NYKYF7A.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/jamf/JamfMigrator/issues/54#issuecomment-640698112", "url": "https://github.com/jamf/JamfMigrator/issues/54#issuecomment-640698112", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

BIG-RAT commented 4 years ago

Updated blurb about permissions on the Wiki page.