Device Management Deployment Scenarios<\/strong><\/h2>\n\n\n\nScenario 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
\n- User identities live, and are managed in an existing, external IdP like Azure AD, Google Workspace, or Okta.<\/li>\n\n\n\n
- Sync the user identities into JumpCloud using a Cloud Directory, or SCIM integration.<\/li>\n\n\n\n
- Once the users are synced, and are logging into their device for the first time, they\u2019ll be redirected to authenticate to the external IdP via JumpCloud federation.<\/li>\n\n\n\n
- The local user account will then be created on the device, and become managed by JumpCloud.\u00a0<\/li>\n\n\n\n
- The user will create a local passcode to access their device. This passcode can be reset from the login window by authenticating through the external IdP.<\/li>\n<\/ol>\n\n\n\n
Device password<\/strong>: Local credentials<\/p>\n\n\n\nZero Trust Controls<\/strong>: IdP<\/p>\n\n\n\nMFA<\/strong>: IdP<\/p>\n\n\n\nScenario 2: Device Management with IdP Password Sync<\/strong><\/p>\n\n\n\n<\/strong><\/p>\n\n\n\nIdentity 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
\n- User identities live, and are managed in an existing, external IdP like Okta.\u00a0<\/li>\n\n\n\n
- Sync the user identities into JumpCloud using a Cloud Directory, or SCIM integration.\u00a0<\/li>\n\n\n\n
- Once the users are synced, and are logging into their device for the first time, they\u2019ll be redirected to authenticate to the external IdP via JumpCloud federation.\u00a0<\/li>\n\n\n\n
- The local user account will then be created on the device, and become managed by JumpCloud.\u00a0<\/li>\n\n\n\n
- The user\u2019s password is managed by the external IdP, and then synced to the JumpCloud account.\u00a0<\/li>\n\n\n\n
- User password changes, and resets have to be done in the IdP.<\/li>\n<\/ol>\n\n\n\n
Device password<\/strong>: IdP<\/p>\n\n\n\nZero Trust Controls<\/strong>: IdP<\/p>\n\n\n\nMFA<\/strong>: IdP<\/p>\n\n\n\nScenario 3: Device Management with JumpCloud Password Sync and External IdP Login<\/strong><\/p>\n\n\n\n<\/strong><\/p>\n\n\n\nIn 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
\n- User identities live, and are managed in an existing, external IdP like Azure AD, or Google Workspace.\u00a0<\/li>\n\n\n\n
- Sync the user identities into JumpCloud using a Cloud Directory, or SCIM integration.\u00a0<\/li>\n\n\n\n
- Once the users are synced, and are logging into their device for the first time, they\u2019ll be redirected to authenticate to the external IdP via JumpCloud federation.\u00a0<\/li>\n\n\n\n
- The local user account will then be created on the device, and become managed by JumpCloud.\u00a0<\/li>\n\n\n\n
- The user\u2019s password is managed by JumpCloud, or on the device itself, and then synced to the IdP.<\/li>\n<\/ol>\n\n\n\n
Device password<\/strong>: JumpCloud<\/p>\n\n\n\nZero Trust Controls<\/strong>: IdP<\/p>\n\n\n\nMFA<\/strong>: IdP<\/p>\n\n\n\nFAQ<\/h2>\n\n\n\n