Configure Account-Driven Enrollment

This article explains how to enable and configure account-driven user enrollment within the JumpCloud Admin Portal. You must configure enrollment before users are able to enroll their iOS and iPadOS devices to be managed by your organization.

Account-driven enrollment is the preferred method for enrolling Apple iOS/iPadOS devices into JumpCloud MDM. With this method, end users can enroll their devices directly by using a Managed Apple Account provided by your organization instead of downloading a profile from an external link or scanning of a QR code in the JumpCloud User Portal.

Considerations:

• Account-driven user enrollment is supported on iOS/iPadOS 15 and later.
• Account-driven user enrollment on macOS and visionOS is not supported in JumpCloud at this time.
• Account-driven device enrollments are not supported in JumpCloud at this time.

Prerequisites:

• Users must have a Managed Apple Account (formally known as Managed Apple ID, or MAID) associated with their JumpCloud user account. Jump to Creating Managed Apple Accounts

Creating Managed Apple Accounts

First, create Managed Apple Accounts either through federated authentication between Apple and your identity provider (Google Workspace, Microsoft Entra ID, or other)*, or manually in Apple Business Manager or Apple School Manager.

*Federation between Apple and JumpCloud is in active development.

After the Managed Apple Accounts are created, they need to be associated with JumpCloud user accounts. See Run the MAID Import Script for instructions.

Next, set up a well-known URL on your domain. Depending on the method you choose, you will host an enrollment file at this URL directly or you will place a redirect from this URL to the JumpCloud service discovery URL.

Setting Up a Well-Known URL

Prerequisites:

• The well-known URL must be hosted on a domain that can handle HTTP GET requests and is the same domain that your end users sign in to. This allows devices to initiate a service discovery process to retrieve the information and direct your users to the JumpCloud enrollment endpoint.

On your web server, implement the following well-known URL for MDM service discovery, replacing yourdomain.com with your org's domain:

https://yourdomain.com/.well-known/com.apple.remotemanagement

Next, configure the redirect from this URL or host a file at this URL.

Configuring a Redirect

To configure account-driven user enrollment using a redirect:

1. Log in to the JumpCloud Admin Portal.
2. Go to DEVICE MANAGEMENT > MDM.
3. On the Apple > Home tab, scroll to iOS Enrollment.
4. Under Account-driven User Enrollment Configuration, select Redirect.
   
5. On your web server, define a redirect rule from the well-known URL you implemented above to the JumpCloud service discovery URL, making sure to place your JumpCloud org ID accordingly.
   • From: https://yourdomain.com/.well-known/com.apple.remotemanagement
   • To: https://apple.mdm.jumpcloud.com/account-driven-service-discovery?organization_id=XXXXXXXXXXXXXXX

Configuring a Redirect in Cloudflare

See Cloudflare's Create rule in the dashboard for more information on this process.

To set up a redirect using Cloudflare Rules:

1. Log in to your Cloudflare account.
2. Select the domain you want to redirect.
3. From the Rules tab, click Redirect Rules.
4. Click Create Rule and give the rule an descriptive name.
5. Under When incoming requests match, select Wildcard pattern.
6. In the Request URL field, enter https://example-domain.com/.well-known/com.apple.remotemanagement* where example-domain.com is your root domain. Remember to include the asterisk after com.apple.remotemanagement.
7. In the Target URL field, enter https://apple.mdm.jumpcloud.com/account-driven-service-discovery?organization_id=XXXXXXXXXXXXXXXXXXXXX where XXXXXXXXXXXXXXXXXXXXX is replaced with your JumpCloud org ID.
8. For Status Code, choose 301.
9. Leave Preserve Query String unchecked.
10. Click Deploy.

Once the redirect rule is active, any requests to the specified path will be redirected to the specified URL. It may take some time for the rule to take effect due to Cloudflare's caching.

Configuring a Redirect in Shopify

See Shopify's Creating and managing URL redirects for more information on this process.

To set up a URL redirect in Shopify:

1. From your Shopify admin, go to Settings > Apps and sales channels.
2. From the Apps and sales channels page, click Online store.
3. Click Open sales channel.
4. Click Navigation.
5. Click View URL Redirects.
6. Click Create URL redirect.
7. In Redirect from, enter /.well-known/com.apple.remotemanagement
8. In Redirect to, enter https://apple.mdm.jumpcloud.com/account-driven-service-discovery?organization_id=XXXXXXXXXXXXXXXXXXXXX where XXXXXXXXXXXXXXXXXXXXX is replaced with your JumpCloud org ID.
9. Click Save redirect.

Configuring a Redirect in Squarespace

See Squarespace's URL mappings documentation for more information on this process.

To set up a URL redirect in Squarespace:

1. Open Developer Tools.
2. Click URL Mappings.
3. Click into the text field to add the redirect, following this format, where XXXXXXXXXXXXXXXXXXXXX is replaced with your JumpCloud org ID:

4. Click Save.

Configuring a Self-Hosted File

Although a self-hosted file is less flexible than a Redirect, it may be useful if you do not have access to your web server configuration.

To configure account-driven user enrollment using a self-hosted file:

1. Log in to the JumpCloud Admin Portal.
2. Go to DEVICE MANAGEMENT > MDM.
3. On the Apple > Home tab, scroll to iOS Enrollment.
4. Under Account-driven User Enrollment Configuration, select Self Host.
   
5. A JSON configuration snippet appears. Click Download JSON.
6. Publish the file on the well-known URL you created above.

Setting up a Web Server to Host the File

To host the JumpCloud enrollment information on a web server, you must define the path to your web server. If the verified domain you use for Managed Apple Accounts is already configured to host files, you can host the enrollment information at the same hosting location. If your environment is not configured to do so, you must set up a web server to host the information.

Prerequisites:

• The web server must have the same fully qualified domain name (FQDN) as the verified domain that the Managed Apple Accounts belong to, and web services must be enabled.
• The SSL certificate for the web server must be issued by a trusted certificate authority. For a list of trusted root certificates, see Apple's List of available trusted root certificates.
• The JSON file must be hosted on a server that supports HTTPS GET requests. Requests contain query parameters, such as user-identifier and model-family, which are passed through to JumpCloud when the device is redirected for enrollment.

The resulting URL for the file must be similar to the following, where example_domain.com is the same format and domain as the Managed Apple Accounts' email address: https://example_domain.com/.well-known/com.apple.remotemanagement

Configure the server to return the appropriate Content-Type header with the file, as follows: Content-Type is 'application/json'

Testing the Enrollment Configuration

To test your configuration:

1. Back in the JumpCloud Admin Portal, under Under Account-driven User Enrollment Configuration, enter your domain in the Input domain field and click Confirm.
2. If successful, the JumpCloud Admin Portal returns a success message: "Account-driven Configuration Successful for {Entered Domain}"
3. Alternatively, if incorrectly configured, you will receive an error message similar to the following: “An error occurred. Account-driven Configuration for {Entered Domain} could not be verified.”

Troubleshooting Error Messages

• Verification failed to get a well-known URL. Please check your info and try again. - Invalid domain entered. Check the configuration.
• An issue occurred during verification. Refer to the help article for remediation tips. - A status code other than 200 was returned. Check the configuration.
• During verification, an unexpected content type was returned. Please check your info and try again. - Content not in JSON format was returned.
• Either unknown content or improper content length was detected during verification. Refer to the help article for remediation tips. - Response length received from the domain was too large. Check the configuration, as we expect a simple JSON response.
• Verification failed to read the response body. Refer to the help article for remediation tips. - Unreadable data in response. Check whether the response contains the proper data.
• Verification failed to understand the JSON response. Refer to the help article for remediation tips. - Readable data was returned in unexpected JSON format. Check the JSON configuration.
• There was an invalid configuration of a well-known URL response during verification. Refer to the help article for remediation tips. - Either the version or baseurl parameters in the JSON configuration is incorrect.
• There were too many redirects during verification. Refer to the help article for remediation tips. - Check that the well-known url is properly redirected and not in a redirection loop.

After ADUE has been configured in the Admin Portal, users can follow the steps to enroll their devices (iOS 15+). See Users: Enroll Your Personal iOS Device.