{"id":87648,"date":"2023-06-05T13:10:31","date_gmt":"2023-06-05T17:10:31","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=support&p=87648"},"modified":"2023-06-12T19:02:06","modified_gmt":"2023-06-12T23:02:06","slug":"use-system-context-authorization-with-jumpcloud-apis","status":"publish","type":"support","link":"https:\/\/jumpcloud.com\/support\/use-system-context-authorization-with-jumpcloud-apis","title":{"rendered":"Use System Context Authorization with JumpCloud APIs"},"content":{"rendered":"\n

JumpCloud administrators can utilize the System Context API to perform system device auto-scaling with JumpCloud. Actions can range from binding the system associations (direct, group, etc.) to shutdown hooks for destroying associations and deleting the system instance. System Context Authorization also lets JumpCloud administrators automate the binding and removal of users to JumpCloud-managed, UNIX-based systems.<\/p>\n\n\n\n

<\/p><\/div>

Note:<\/strong> \n

Systems that have been automatically enrolled using Automated Device Enrollment (ADE), MDM enrollment, or systems enrolled using the User Portal install are not eligible to use the System Context API. Systems enrolled in these ways are unable to use the System Context API to prevent unauthorized access to system groups and resources. If a script that utilizes the System Context API is invoked on a system enrolled in such a way, it will error with an unauthorized message.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n