Support Center

How the JumpCloud Agent Works

Features


The JumpCloud agent has several capabilities as it relates to your systems:
  • Supports multiple flavors of Linux, Mac, and Windows (see here for a complete list)
  • Has the ability to add, modify, and delete local user accounts, including settings passwords, updating full name fields, and changing group membership. Because the JumpCloud agent manages local user accounts, a loss of Internet access will not prevent users from logging in - though you won't be able to make changes on that host via JumpCloud's console or API.
  • Can "take over" management of existing user accounts on a system when the user name in JumpCloud matches the (short) user name on the system.
  • (Linux only) Can enable multi-factor authentication via SSH with user name and password, leveraging Google Authenticator.
  • (Mac and Linux only) Has the ability to create and manage local system groups and their members.
  • Can run commands that you specify in JumpCloud Commands. On Mac and Linux, commands are run in the shell. On Windows, you can choose between cmd and PowerShell. Commands can be run either immediately, on a schedule, or based on an external event such as a user being added or removed, or based on JumpCloud's receipt of an inbound web-hook.

Architecture


The JumpCloud agent is written in Go (with a bit of C++ in Windows). It has a memory footprint of approximately 5-7MB of RAM and runs as a compiled native binary.

It contacts JumpCloud's servers (see here for a list of endpoints the agent contacts) using a long HTTPS poll every 60 seconds looking for new work to do. If work is available, the agent downloads the work request, and executes it.


Connect Key


The Connect Key in JumpCloud provides you with a means of associating your systems to your JumpCloud organization. Each JumpCloud Administrator has a unique Connect Key; although this is not considered a secret and any Key can be used to deploy the agent to a system. 


Log Files


JumpCloud agent log files can be found in:
  • Linux and Mac: /var/log/jcagent.log
  • Windows: C:\Windows\Temp\jcagent.log


Installation


See Getting Started: Systems


Updates


Updates are pushed to existing systems where the agent is deployed and active. If the system is not active during the update cycle, the update will be queued to push to the system the next time it becomes active. The agent may not receive the update if a condition exists causing the update to fail multiple times, if this happens, manual intervention may be required. An update can be executed manually be running the agent installation as normal. Agent version is found in:

  • /opt/jc/version.txt
  • C:\Program Files (x86)\JumpCloud\plugins\contrib\version.txt


Uninstallation


See How to Uninstall the JumpCloud Agent
 

Last Updated: Oct 25, 2017 02:56PM MDT

Related Articles
31b11a79e2c94470a66430cfe6d3eecd@jumpcloud.desk-mail.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete