On 6/19/2018, support for TLS 1.0 will end for all JumpCloud service endpoints. Note: The JumpCloud agent will NOT be affected by this change.
Action Recommended: On 6/5/2018 we will implement the changes deprecating TLS 1.0 for all JumpCloud services during a 90-minute test window between 14:00 UTC and 15:30 UTC to allow for testing any clients and applications that may be using the protocol. During this window, if you experience any service outage while not explicitly testing for TLS 1.0 usage, the service affected may be using the protocol and as of 6/19/2018 will cease to function permanently unless further action is taken.
Either accessing https://console.jumpcloud.com or SAML applications. Up to date, supported browsers will be unaffected.
Using ldap.jumpcloud.com. Due to both the amount and variations of LDAP applications that can integrate with JumpCloud, we are unable to provide specific guidance. Check with the application vendor that TLS 1.0 is not used by default. In lieu of application documentation or vendor support, a packet capture can also determine what protocol is in use. E.g., with Wireshark capturing port 636:
REST API Integrations
Any other client applications using the JumpCloud API endpoints may be affected. This could include Go, Ruby, CURL, Python, Powershell, etc... Please check the applicable vendor documentation to determine if updates are required. A packet capture on port 443 similar to the LDAP example can also determine the protocol being used.