When you create a configuration profile, you can either save the file locally or upload it to Jamf Pro. If uploading to Jamf Pro, keep the following in mind:
Configurations must be saved in .mobileconfig format.
Profile file names cannot match an already existing name of a configuration profile in Jamf Pro.
You cannot upload updates to an already existing configuration profile with the same name.
An integration with your cloud identity provider and required values from the integration (for example, client ID). For instructions, see Jamf Connect Identity Provider Integrations.
- Uploading a configuration profile to Jamf Pro requires the following:
Credentials to a Jamf Pro user account with administrator privileges.
The Classic API must have basic authentication allowed under Password Policy in your Jamf Pro settings.
To upload a configuration profile saved locally to Jamf Pro, the profile must be signed.
- In Jamf Connect Configuration, click the + icon at the bottom-left of the window.
- Name your new configuration by clicking on it in the sidebar.
- Click the Identity Provider tab.
- Configure authentication settings:
- (Optional) Configure advanced authentication settings in the Okta or OIDC settings sections.
- Click the Login tab.
- Configure settings for the login window, including user creation settings.
- Click the Connect tab.
- Configure settings for Self Service+, including Kerberos integration settings.
- (Optional) Click the </> button in the top-right and do the following:
- Click the Test button to confirm that your authentication settings are correctly configured.
- (Optional) Save and export your configuration profile.
If you selected the Jamf Pro Upload checkbox, the configuration profile is automatically uploaded to Jamf Pro.