Support Center

JumpCloud Agent Compatibility, System Requirements, and Impacts

This document details operating system compatibility and associated system impacts of the JumpCloud agent. 
 

Mac
Windows
Linux

 

Mac


Supported Versions: 10.11, 10.12, 10.13

Disk Usage: ~14 MB
Memory Usage:  ~5 MB 
Dependencies: none
Installed Services: jumpcloud-agent
Filesystem:
  • /opt/jc/ - Primary location of jcagent
  • /var/log/jc*, /opt/jc/*.log - Agent log files tracking logged events at install time and during normal processing
  • /Library/Preferences/com.apple.loginwindow.plist
  • /Library/Security/SecurityAgentPlugins/jumpcloud-loginwindow.plist
  • Additional filesystem impacts
Additional Considerations
 
 

Windows


Note: International versions of Windows are supported, however, certain international character sets may cause cosmetic issues in the Systems detail views and/or adverse results in Command execution in the Admin Console. 

Supported Versions: 7, 8, 8.1, 10 (32 and 64 bit) Server 2008 R2 (32 and 64 bit) 2012, 2016 (64 bit)
Disk Usage: ~47 MB (incl. dependencies)
Memory Usage:  ~6 MB
Dependencies: MS Visual C++ 2013 Redistributable package (x86_64)
Installed Services: JumpCloud Agent (jumpcloud-agent) / Automatic startup
Filesystem:
  • C:\Program Files\JumpCloud - Primary location of jcagent for 32 bit
  • C:\Program Files (x86)\JumpCloud - Primary location of jcagent for 64 bit
  • C:\Windows\Syswow64\Usermgmt.dll
  • C:\Windows\Temp\jcagent.log - Agent log files tracking logged events at install time and during normal processing)
  • C:\Users\user\AppData\Local\Temp\jcagent.log - Installation log

Registry: 
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JumpCloud\JumpCloud Agent\ConfigFile
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{96542816-DAD1-4D02-8363-CA4121E5CAE7}_is1

Additional Considerations
 
 

Linux


Supported Versions: 
  • CentOS: 6, 7
  • Red Hat Enterprise Linux (RHEL): 6, 7
  • Debian: Jesse (8.0) (64 bit), Stretch (9.0)
  • Ubuntu: 14.04,16.04 (64 bit)
  • Amazon® Linux: 2013.09, 2014.03, 2014.09, 2015.03, 2015.09, 2016.03, 2016.09, 2017.03, 2017.09

Disk Usage: ~14 MB
Memory Usage:  ~5 MB 
Dependencies: 
  • Ubuntu - apt-rdepends apt-show-versions coreutils curl dpkg grep hostname libc-bin lsb-release lsof mawk passwd procps sysv-rc sysvinit-utils tar auth-client-config
  • CentOS/RHEL 6, 7 - chkconfig coreutils curl findutils gawk glibc-common grep initscripts lsof net-tools rpm shadow-utils tar util-linux which yum sudo policycoreutils
  • Amazon Linux - chkconfig coreutils curl glibc-common grep initscripts lsof net-tools rpm shadow-utils tar util-linux yum sudo

Installed Services: jumpcloud-agent, agent-monitor
Filesystem:
  • /opt/jc/ - Primary location of jcagent
  • /etc/init.d/jcagent - Service start and stop script
  • <LIB_DIR>/security/pam_google_authenticator.so - The Google auth pam plugin <LIBDIR> is the OS and arch lib dir eg: /lib, /lib64, etc...
  • /var/log/jc*, /opt/jc/*.log - Agent log files tracking logged events at install time and during normal processing
  • /etc/rsyslog.d/jumpcloud.conf - JumpCloud appends a local host address (127.0.0.1:14028) when enabling Syslog for the Events API (logging user events).  For more information, refer to our KB for JumpClouds Events API
  • Additional filesystem impacts
Additional Considerations

Additional Filesystem Impacts

Depending on the configuration choices for users and systems within the JumpCloud console, additional existing files may be modified by the JumpCloud agent:
 
  • /etc/ssh/sshd_config - one or more of the following parameters: [ PermitRootLogin, PasswordAuthentication, UsePAM, PubkeyAuthentication, ChallengeResponseAuthentication]
  • /etc/pam.d/sshd, /etc/pam.d/system-auth, /etc/pam.d/password-auth - JumpCloud adds the pam_google _authenticator.so plugin line to one of these files depending on your Linux distro. Existing installations of this library may cause a conflict
  • /etc/ssh/jumpcloud/totp/${USER} - TOTP key files are stored on a per user basis at this path
  • /etc/sudoers.d - JumpCloud appends sudo users to /etc/sudoers.d
  • /root/.ssh/authorized_keys, /home/<USER>/.ssh/authorized_keys - JumpCloud manages this based on users having uploaded public keys to JumpCloud
  • See also: JumpCloud Keeps Reverting My Changes to sshd_conf

Additional Considerations
 

Last Updated: Nov 16, 2017 01:26PM MST

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