Managed Apple Accounts are the gateway to Bring Your Own Device (BYOD) Programs. These accounts, created within Apple Business Manager (ABM), or using JumpCloud’s SSO and SCIM Connector, are required for managing user-owned devices with JumpCloud.
Use JumpCloud OIDC Single Sign On (SSO) to give your users convenient but secure access to their Managed Apple Account with a single set of credentials. Automatically provision, update and deprovision users in ABM from JumpCloud, centralizing user lifecycle and user identity management in JumpCloud for ABM. Save time and avoid mistakes, as well as potential security risks, related to manually creating users.
Read this article to learn how to setup the ABM integration.
Prerequisites
- A JumpCloud administrator account
- JumpCloud SSO Package or higher or SSO Ă la carte option
- An ABM account with the role of Administrator or People Manager
- An Apple verified domain and federated authentication
- If federated authentication is not already enabled, setting up SSO will automatically enable it
- If you have an existing ABM connector, either prebuilt or custom OIDC, you must deactivate and delete the existing connector before configuring this connector
- The JumpCloud user's Managed Apple ID attribute field should be populated for users where the desired email address is different from their company email
- SCIM must be enabled in the ABM Directory Sync settings
- Domains must be fully captured prior to them being locked in ABM, a pre-requisite for enabling federation and directory sync. This domain capture can take up to a month
- Admin accounts cannot be federated
- Non-administrative users whose unmanaged ABM accounts are associated with a company domain email address should manually update them to a non-company domain email address before the end of the domain capture period. Otherwise, ABM will automatically assign an auto-generated email address to these accounts
- Safari is not a supported browser for this configuration flow as some of the ABM pages do not render
- The ABM Application should not be placed behind a managed device conditional access policy if this federation will be used for device enrollment flows
SCIM Considerations
- All newly provisioned users will have the default role of staff
- A user’s email address must belong to an Apple verified domain for them to be created and updated through SCIM
- It is recommended to set your Client Secret's expiration to 12 months
You may not receive an alert when your token is about to expire. Set a reminder in your calendar to refresh your token before the expiration date.
- If you need to update your secret, you must deactivate the IdM integration, update the secret, and then reactivate the IdM integration
- Password synchronization is not supported
Attribute Considerations
- A default set of attributes are managed for users. See the Attribute Mappings section for more details
- The following attribute is not supported by JumpCloud:
- division
Creating a new JumpCloud Application Integration
- Log in to the JumpCloud Admin Portal.
- Navigate to USER AUTHENTICATION > SSO Applications.
- Click + Add New Application.
- Type the name of the application in the Search field and select it.
- Click Next.
- In the Display Label, type your name for the application. Optionally, you can enter a Description, adjust the User Portal Image and choose to hide or Show in User Portal.
- Click Save Application.
- Click Configure Application.
Configuring the SSO Integration
To configure JumpCloud
- On the SSO tab of the ABM connector, click Activate.
- Copy the Client ID and Secret.
The Client ID and Secret (token) may only be shown once. Copy them to a secure location, like the JumpCloud Password Manager, for future reference.
- Click Got It.
To configure Apple
Federating a Domain that already has Managed Apple Accounts takes up to 30 days. For more information, please consult Apple's Documentation.
- Log into Apple.
- Go to My Profile > Managed Apple Accounts.
- Click Get Started.
- Select Custom Identity Provider and enter the following information:
- Name - <name of your connector>
- Client ID - copy and paste the Client ID generated in the previous section
- Client Secret - copy and paste the Client Secret generated in the previous section
- SSF Config URL - enter https://ssf.jumpcloud.com/.well-known/ssf-configuration
- OpenID Config URL - enter https://oauth.id.jumpcloud.com/.well-known/openid-configuration
- Click Continue and then Sign in with <name of your connector>.
If you do not see Sign in with <name of your connector> and are using a non-Safari browser, switch to Safari to complete the configuration.
- When signed in, click Continue.
- Under User sign in, ensure it shows Connected.
Authorizing User SSO Access
Users are implicitly denied access to applications. After you connect an application to JumpCloud, you need to authorize user access to that application. You can authorize user access from the Applications, Users List or User Groups page.Â
To authorize user access from the Application’s page
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
- Select the User Groups tab. If you need to create a new group of users, see Get Started: User Groups.
- Select the check box next to the desired group of users to which you want to give access.
- Click Save.Â
To learn how to authorize user access from the Users or User Groups pages, see Authorize Users to an SSO Application.
Validating SSO user authentication workflow(s)
IdP-initiated user workflow
- Access the JumpCloud User Console
- Go to Applications and click an application tile to launch it
- JumpCloud asserts the user's identity to the SP and is authenticated without the user having to log in to the application
SP-initiated user workflow
- Go to the SP application login - generally, there is either a special link or an adaptive username field that detects the user is authenticated through SSO
This varies by SP.
- Login redirects the user to JumpCloud where the user enters their JumpCloud credentials
- After the user is logged in successfully, they are redirected back to the SP and automatically logged in
Configuring the Identity Management Integration
To configure Apple
- In ABM, navigate to Directory Sync > Custom Sync and click Enable.
- In Authorization callback URL - enter https://console.jumpcloud.com/api/v2/provision/applebusinessmanager/callback
- Click the + Client Secret link and select 12 months (recommended).
- Click Save.
- Copy the Client ID and Client Secret.
The Client ID and Secret (token) may only be shown once. Copy them to a secure location, like the JumpCloud Password Manager, for future reference.
You may not receive an alert when your secret is about to expire. Set a reminder in your calendar to refresh your secret before the expiration date.
- Click Done.
To configure JumpCloud
- Create a new application or select it from the Configured Applications list.
- Select the Identity Management tab.
- Click Configure.
- You're presented with two fields:
- Client ID - enter the Client ID generated in the previous section
- Client Secret - enter the Client Secret generated in the previous section
- Click Activate.
- If the status of the sync in Apple is green, the sync has been successfully set up.
- You can now connect user groups to the application in JumpCloud to provision the members of that group in ABM. Learn how to Authorize Users to an Application.
Attribute Mappings
The Export Attributes Mapping table lists the Required and Optional Mappings that JumpCloud sends to the Service Provider. See Attribute Considerations for more information regarding attribute mapping considerations.Â
Learn about JumpCloud Properties and how they work with system users in our API.
Modifying User Attributes
It's highly recommended you use all optional mappings. This creates a more complete user profile, enabling better automation and more accurate access management within the application.
To add user attributes
- From your connector’s configuration page, select the Identity Management tab.
- Expand the Export Attribute Mapping section and click Edit. The Optional Mappings table will open.
- Scroll to the bottom of the table and click +Add Attribute.
- Select one of the mapping types:
- Direct Mapping (JSON Path) - send the value from a user attribute in JumpCloud directly to an attribute in the service provider
- From the JumpCloud Attribute dropdown, select the desired attribute
- If you choose “Custom User Attribute” you must type the name of the attribute exactly as it on the user details page. To see the dropdown again, you must delete the attribute and add a new attribute
- From the SCIM Attribute dropdown, select the corresponding (destination) attribute
- From the JumpCloud Attribute dropdown, select the desired attribute
- Expression - transform or combine multiple user attributes into a single, custom value before sending it to the service provider
- Enter the expression in the JumpCloud Attribute field
- From the SCIM Attribute dropdown, select the corresponding (destination) attribute
- Constant - send a fixed, predefined value—like a specific company name —for every user to the service provider
- This is a free text field with no validation, e.g., the attribute must match exactly, including case, to the corresponding attribute in the user record. Once the custom attribute is added, you must delete it and readd a new custom attribute to see the dropdown again.
- Direct Mapping (JSON Path) - send the value from a user attribute in JumpCloud directly to an attribute in the service provider
- Repeat these steps for additional attributes.
- Click Preview Mappings to review the User Schema.
- If you do not select a specific user from the Preview Filter dropdown, the schema will default to the first user.
- Click Update.
Updates to the user schema will not dynamically sync. To force a sync, you must modify the user group’s record in some way, like adding a space to the Description field.
To modify existing user attributes
This new functionality is in Private Preview. Contact your Account Manager to enable it. Your feedback helps us evolve this feature so share your suggestions at the bottom of the article. Learn More
This enhancement gives you complete control over the user attributes sent from JumpCloud to this application. You can now:
- Fully control mappings - define which JumpCloud attribute or source data corresponds to an attribute in the SP's SCIM schema
- Use a variety of source values - map data from the user's standard attributes, Manager field, custom attributes, or other data sources
- Manipulate data with expressions - transform data, such as preferred first names and date format, using expressions before transmission to the SP. Learn more
- Preview changes - review your new mappings to ensure accuracy before you save
- From your connector’s configuration page, select the Identity Management tab.
- Expand the Export Attribute Mapping section and click Edit.
- For the type of attribute you would like to modify:
- Direct - select the new attribute from the dropdown(s)
- Expression - click in the Expression field and make the desired edits. If necessary, select the new attribute from the SCIM Attribute dropdown
- Custom - delete the existing values in either or both of the attribute fields and enter the new values
- Click Preview Mappings to review the updated User Schema.
- Click Update.
Updates to the user schema will not dynamically sync. To force a sync, you must modify the user group’s record in some way, like adding a space to the Description field.
To delete user attributes
- From your connector’s configuration page, select the Identity Management tab.
- In the Export Attribute Mapping section, click Edit. The Optional Mappings table will open.
- Click Delete (
) to remove any optional attributes.
- When finished, click Update.
Attributes that were initially included and populated in the user record and then deleted at a later time will not be modified or removed from the user record.
To restore the default Optional Mappings, click Edit > Restore Defaults > Update.
ABM User Attributes
JumpCloud Property | JumpCloud UI | SCIM v2 Mapping | ABM Value |
---|---|---|---|
firstname | First Name | name.givenName | First name |
lastname | Last Name | name.familyName | Last name |
Company Email | emails [work] | email address | |
department | Department | department | Department |
employeeIdentifier | Employee ID | [urn:ietf:params:scim:schemas:extension:enterprise:2.0:User]. employeeNumber | Person Number |
costcenter | CostCenter | [urn:ietf:params:scim:schemas:extension:enterprise:2.0:User]. costcenter | Cost center |
SCIM Directory Insights Events
The following Directory Insights (DI) events provide visibility into failures and detailed information about the user and group data being added or updated from HR or other external solutions to JumpCloud.
Customers with no package or the Device Management Package will need to add the Directory Insights Ă la carte option. Directory Insights is included in all other packages.
SCIM DI Integration Events
Event Name | Event Description |
---|---|
idm_integration_activate | Logged when an IT admin attempts to activated new SCIM Identity Management integration. |
idm_integration_update | Logged when an IT admin attempts to update a configured and activated SCIM Identity Management integration. |
idm_integration_reauth | Logged when an IT admin attempts to change the credentials for an activated SCIM Identity Management integration. |
idm_integration_delete | Logged when an IT admin attempts to deactivate an activated SCIM Identity Management integration. |
SCIM DI User Events
Event Name | Event Description |
---|---|
user_create_provision | Logged when JumpCloud tries to create a new user in service provider application. |
user_update_provision | Logged when JumpCloud tries to update an existing user in service provider application. |
user_deprovision | Logged when JumpCloud tries to change an existing user to inactive in the service provider application. |
user_delete_provision | Logged when JumpCloud tries to delete an existing user in service provider application. |
user_lookup_provision | Logged when JumpCloud encounters an issue when trying to lookup a user to determine if the user needs to be created or updated. |
Removing the Integration
These are steps for removing the integration in JumpCloud. Consult Apple’s documentation for any additional steps needed to remove the integration in ABM. Failure to remove the integration successfully for both Apple and JumpCloud may result in users losing access to the application.
To deactivate the IdM Integration
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to deactivate and click to open its details panel.
- Under the company name and logo on the left hand panel, click the Deactivate IdM connection link.
- Click confirm.
- If successful, you will receive a confirmation message.
To deactivate the SSO Integration or Bookmark
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to deactivate and click to open its details panel.
- Select the SSO or Bookmark tab.
- Scroll to the bottom of the configuration.
- Click Deactivate SSO or Deactivate Bookmark.
- Click save.
- If successful, you will receive a confirmation message.
To delete the application
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to delete.
- Check the box next to the application to select it.
- Click Delete.
- Enter the number of the applications you are deleting
- Click Delete Application.
- If successful, you will see an application deletion confirmation notification.