Easily onboard new users that have JumpCloud managed devices by integrating your existing Identity Provider (IdP) with JumpCloud. This allows your users to securely access their devices by logging in with their IdP credentials.<\/p>\n\n\n\n
Prerequisites<\/strong><\/p>\n\n\n\n
Considerations<\/strong><\/p>\n\n\n\n
Externally managed passwords prevent password changes within JumpCloud, both by users and admins. When users are set to Password Externally Managed, they will no longer receive password expiration notifications and password expirations will no longer apply to them.
Use this setting when a user\u2019s password is being managed by an upstream integration or when they\u2019re authenticating with an external identity provider (IdP).<\/p>\n\n\n\n
<\/p><\/div>
Note:<\/strong> Once this setting is enabled, users will not be able to change their own password from their JumpCloud device tray application, User Portal, or any other password reset flow. Additionally, admins won\u2019t be able to set user passwords from the Admin Portal.<\/p><\/div><\/div><\/div>\n\n\n\n
Workflow<\/strong><\/p>\n\n\n\n
Scenario 1: Device Management with an External IdP<\/strong><\/p>\n\n\n\n
<\/p>\n\n\n\n
Identity management is kept in your existing IdP. Identities are synced into JumpCloud for the purpose of IdP login. New users will set up and maintain a local passcode on their device. Existing users will maintain their existing passwords after they become managed by JumpCloud. If the user forgets this passcode, it may be reset with an external IdP login. The passcode is stored locally on the device, reducing the risk of compromise and allowing for offline authentication. The user can log in to any web-based resources (like JumpCloud\u2019s User Portal, SSO apps, local account provisioning flows, etc.) with their IdP login.<\/p>\n\n\n\n
Device password<\/strong>: Local credentials<\/p>\n\n\n\n
Zero Trust Controls<\/strong>: IdP<\/p>\n\n\n\n
MFA<\/strong>: IdP<\/p>\n\n\n\n
Scenario 2: Device Management with IdP Password Sync<\/strong><\/p>\n\n\n\n
<\/strong><\/p>\n\n\n\n
Identity management is kept within your existing IdP. Identities are synced into JumpCloud for the purpose of IdP login. Passwords are also synced from your IdP into JumpCloud outside of the OIDC IdP login flow (which doesn\u2019t capture the password). This password is synced to the user\u2019s device, resulting in the IdP password, and the device password being in sync. Optionally, an IdP object can be configured allowing users to log in with their IdP credentials for web-based logins. <\/p>\n\n\n\n
Device password<\/strong>: IdP<\/p>\n\n\n\n
Zero Trust Controls<\/strong>: IdP<\/p>\n\n\n\n
MFA<\/strong>: IdP<\/p>\n\n\n\n
Scenario 3: Device Management with JumpCloud Password Sync and External IdP Login<\/strong><\/p>\n\n\n\n
<\/strong><\/p>\n\n\n\n
In this scenario, identity management is kept within your existing IdP. Identities are synced to JumpCloud for the purpose of IdP login. Users are also associated to a Cloud Directory integration. This enables JumpCloud to own the password, but your IdP to own the identity. Users can change their password from their device, allowing the password to be synced to JumpCloud, and to their IdP. The user will log in with their IdP for web-based logins with the password that\u2019s managed by JumpCloud. Any Zero Trust, MFA, etc. controls will be enforced at the IdP login.<\/p>\n\n\n\n
Device password<\/strong>: JumpCloud<\/p>\n\n\n\n
Zero Trust Controls<\/strong>: IdP<\/p>\n\n\n\n
MFA<\/strong>: IdP<\/p>\n\n\n\n
No. During the federated login flow, JumpCloud does not capture the IdP password.\n<\/p><\/div><\/div>\n\n\n\n
Any resource that supports browser-based logins: User Portal, SSO apps, Self Service Account Provisioning, Mac ADE, and local password resets.<\/p><\/div><\/div>\n\n\n\n
Any resource that does not support browser-based logins: LDAP and RADIUS<\/p><\/div><\/div>\n\n\n\n
Account lockout applies to all users in an organization. If all users will authenticate with an IdP, and therefore use a local device credential, the OS lockout mechanisms may be used. In this case, JumpCloud account lockout doesn\u2019t need to be configured. However, even if JumpCloud account lockout is configured, it can be overridden for individual users on devices by navigating to USER MANAGEMENT<\/strong> > Users<\/strong>, clicking a specific user, then under the User Security Settings and Permissions<\/strong> dropdown, select Bypass account lockout policy for user\u2019s managed device<\/strong>.<\/p>\n<\/div><\/div><\/div>\n\n\n\n
Mac (and Windows): Admins can unlock the account in the Admin Portal, see Unlock User Accounts<\/a> to learn more. <\/p>\n<\/div><\/div><\/div>\n\n\n\n
Yes. You can create a routing policy to have specific groups of users required to authenticate through their IdP. See Routing Policies for Identity Providers<\/a> to learn more. <\/p>\n<\/div><\/div><\/div>\n\n\n\n
Yes, however this will prevent the user self service password reset flow from functioning by obscuring the Self Service Account Provisioning option.\n<\/p><\/div><\/div>\n\n\n\n
The user will not know their local account device password unless they explicitly set it after login with PIN or biometric. This will result in denied logins, and could lead to lockouts by the OS or on the JumpCloud account, if configured.\n<\/p><\/div><\/div>\n\n\n\n
Yes, accounts can be manually bound to devices in the Admin Portal. Use the Password Sync<\/strong> dropdown to determine if the user’s JumpCloud password will be synced to the device or not. For Federated accounts where the user logs into the device with a local password or PIN, set Password Sync<\/strong> to No<\/strong>.
Learn More<\/a><\/p>\n<\/div><\/div><\/div>\n\n\n\n