̽»¨´óÉñ administrators can utilize the System Context API to perform system device auto-scaling with ̽»¨´óÉñ. 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 ̽»¨´óÉñ administrators automate the binding and removal of users to ̽»¨´óÉñ-managed, UNIX-based systems.
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.
- Learn how to use System Context Authorization in our .Ìý
- Administrators can also find links to .
̽»¨´óÉñ administrators can authenticate to a subset of endpoints using System Context Authorization without needing to authenticate to the ̽»¨´óÉñ API with an API key. The endpoints include the following:
- A system may fetch, alter, and delete metadata about itself, including manipulating a system's Group and Systemuser associations
/api/systems/{system_id} | GET PUT
- A system may delete itself from your ̽»¨´óÉñ organization
/api/systems/{system_id} | DELETE
- A system may fetch its direct resource associations under v2 (Groups)
/api/v2/systems/{system_id}/memberof | GET
/api/v2/systems/{system_id}/associations | GET
/api/v2/systems/{system_id}/users | GET
- A system may alter its direct resource associations under v2 (Groups)
/api/v2/systems/{system_id}/associations | POST
- A system may alter its System Group associations
/api/v2/systemgroups/{systemgroup_id}/members | POST
- Note: If a system attempts to alter the system group membership of a different system, the request will be rejected.