Configuring Jamf Connect Login with Microsoft Azure AD

You can configure Jamf Connect Login by setting preference keys.

Preference keys allow for full manipulation of Jamf Connect Login’s features. You can set preferences through multiple methods:

  • Use Jamf Connect Configuration to create a configuration profile.
    For more information, see Jamf Connect Configuration.

  • Manually create a configuration profile with a text editor.

  • Set preferences with the defaults write command.

Note: The defaults command will not show preferences set by an MDM solution.

Jamf Connect Login preference keys must be written in the following location:


Jamf Connect Login does not create this PLIST file. You must create it manually.

If using Jamf Pro, you must sign the configuration profile before uploading. For more information, see the Deploying Custom Configuration Profiles with Jamf Pro Knowledge Base article.

Preference Keys

The following tables contain all the preference key-value pairs that can be set with Jamf Connect Login.

Note: Boolean key-values that are not configured default to false unless stated otherwise.

Required Key-Value Pairs





Specifies Microsoft Azure AD as your IdP.




The Application ID of the registered app in your IdP used to authenticate the user.




The Application ID of the registered app in you IdP used for authenticating the user's password via a resource owner password grant (ROPG) workflow. This value should should usually match the OIDCClientID preference key.



Optional Key-Value Pairs

Optional Key-Value Pairs can be set to further customize the Jamf Connect Login user experience and account creation process.

Account Creation Settings





If set to true, all users become local admins when created on the computer.




Determines if a keychain entry is created for Jamf Connect Verify.




Determines if any existing Active Directory mobile accounts are "demobilized", which is the process of converting a mobile account into a local account.




Determines if users can bypass network authentication and use the Local Auth button at the loginwindow.

If set to true, the Local Auth button is not available, and user must authenticate to their network.

If set to false, the Local Auth button is available, and users can choose to authenticate locally.




Specifies which users can still locally authenticate if DenyLocal is set to true









The contents of a .jamfconnectlicense file encoded in Base64 data format.

Note: Maintaining your license key in a separate configuration profile provided by your account manager is recommended.




Used with DenyLocal to force authentication to the IdP first, but then fallback to local authentication if the IdP is unavailable.




Allows local accounts to be migrated to network accounts.

This is typically used when the user account was already created on the system, but you want the accounts to have the same username and password as the user’s cloud identity.

Jamf Connect Login does this by forcing the user to sign in with their IdP, and then attempts to match the user with an existing local account. Consider the following user migration scenarios:

  • If a user's network username and password match a local username and password, the account is considered migrated. No additional steps are needed.

  • If a user's network username matches a local username but the passwords do not match, the user will be prompted to enter their current local password. Once successfully entered, Jamf Connect Login will use the current local password and the current network password to sync the account to the current network password.

  • If a user's network username does not match any local account, the user will be given the option to create or migrate a local account. To migrate an account, the user must provide the existing local password. At this point Jamf Connect Login will synchronize the password to the network password, and then add the network username as an alias to the local account. This way the user can sign in to the system as their network username.

Additionally, IdPs can migrate users from local accounts to accounts associated with network identity. With the Migrate and DenyLocal preference keys, all subsequent sign-ins will be authenticated to your IdP, and then the system verifies if the user record has an IdPUser attribute. If this attribute cannot be verified, the user will be asked to select a local account to associate with the user’s network account. If the local account shortname does not match the network shortname, the network name will be added as an alias to the account so the user will be able to use either one. This also keeps the home folder path and other elements of the user record the same.

Note: For every successful network authentication of a user, the user’s record will be updated with the “NetworkSignIn” attribute. If the user was only authenticated locally, this attribute will not be updated.




Specifies which local accounts are excluded from the migration pull-down menu







When using the AuthUI rule, determines if the token cache is set to /tmp/cachedata




Specifies a path to a UID tool that allows you to set a local user account's UID to a custom value during account creation. This can be used to match a local user account's UID with a user's LDAP UID attribute. Your UID tool must be an executable script.



OpenID Connect Settings






If set to true, this key prompts users to create a new password for their new local account.

If set to false, this key prompts users to re-enter their network password, which also becomes the local account password. This ensures a user's network and local password are synced during user creation.

Note: This key is set to true by default.




Specifies which user groups become local admins during account creation. You can specify one user group as a string or multiple user groups in an array of strings.

Note: By default, Jamf Connect Login reads the "groups" attribute in a user's ID token to determine if they become a local admin. To use a different attribute to determine user creation, see the OIDCAdminAttribute preference key.














Specifies what attribute stored in an ID token is used to determine if a user is created as a standard or admin local user. By default, Jamf Connect Login will read the "groups" attribute for any values specified with the OIDCAdmin preference key.




The client secret used by Jamf Connect Login and your IdP.




When set to true, Jamf Connect Login will use local authentication by default rather than cloud authentication, which ensures users can always log in without a network connection.




When set to true, Jamf Connect Login will ignore any roles that exist in your IdP. This key ensures local user accounts maintain their current status as either an admin or standard account.

When set to false or unspecified, Jamf Connect Login will read the OIDCAdmin key for configured roles and will change a local user account status based on any roles in your IdP.




The redirect URI used by your Jamf Connect app in your IdP.

"" is recommended by default, but any URI value may be used as long as the configured value in IdP matches the value in your Jamf Connect Login configuration profile.




Specifies the Tenant ID for your organization that's used for authentication.




Your IdP's OpenID metadata document that stores OpenID configuration information. This value appears in the following format: ""

Note: This key is required if the OIDCProvider key is set to "Custom".




Ignores any cookies stored by the loginwindow



Pluggable Authentication Module (PAM)





Specifies your Identity Provider (IdP) for use with PAM.




The Client ID of the created app in your IdP used to authenticate the users.




The Redirect URI used by the created app in your IdP




Specifies which tenant in your IdP to use with PAM.

Note: If Okta is your IdP, this key is required.




The client secret of your Jamf Connect app in your IdP. This value is only known by Jamf Connect and your IdP.



Messaging and Appearance Settings





Path to a locally stored image to use as a background for the login window




Path to a locally stored image to use as a logo during password validation or local password creation

Note: A 250 x 250 pixel image is recommended.



Help Settings




AllowNetwork Selection

When set to true, this preference key allows users to configure and confirm their network connection preferences from the login window. To access this feature when enabled, users can click Network Connection in the bottom-right corner of the login window.

Note: To ensure the security of computers, users cannot select an open Wi-Fi network at the login window.




Specify a URL to display at the login window that directs user's to a resource for onboarding or enrollment help.




Add a custom image to use as a clickable logo for the Help URL.

Note: The HelpURL key must be specified.




A path to a local file that users can access by clicking the "Help" button in the Jamf Connect Login window. This file is only displayed if the computer cannot connect to the internet and access the URL specified with the HelpURL key.

Note: Supported file types include PDF and HTML.



FileVault Settings
If enabling FileVault on computers with Jamf Connect, see the Using FileVault with Jamf Connect Knowledge Base article.





If set to true, FileVault will be enabled for the first user that logs in to a computer.




If set to true, Jamf Connect will store the FileVault recovery key to /var/db/NoMADFDE unless otherwise specified.




Specifies a custom file path for the FileVault recovery key



EULA Settings

Note: The EULA mechanism must be enabled before configuring EULA preferences. To add the EULA mechanism to Jamf Connect Login, see End User License Agreement.





Specifies a file where the end user's license agreement record (EULA) is stored.




Text used for the EULA


<string>Insert EULA text here</string>


Title of the EULA text


<string>User Agreement</string>


Subtitle of the EULA text


<string>Terms and Conditions</string>

Script Settings

Note: The RunScript mechanism must be enabled before configuring script preferences. To add the RunScript mechanism to Jamf Connect Login, see Login Script.





The arguments used with a specified script run by the RunScript mechanism

Note: The ScriptPath key must bey specified.







Specifies the path to the script or other executable run by the RunScript mechanism. Only one script can be used with Jamf Connect Login at any time.



Hybrid Identity

These keys can be used to separate the authentication process completed via OpenID Connect from the password verification process completed by the Resource Owner Password Grant (ROPG), which is required to configure Jamf Connect with hybrid identity solutions.

For more information about configuring hybrid identities with Azure AD see the following Knowledge Base articles:





Specifies where ROPG authentication will occur. Supported values are the following:

  • Custom

  • Azure_v2

Set this value to "Custom" if using Azure AD with AD FS.

Set this value to "Azure_v2" if you are using password hash synchronization or pass-through authentication, which allows Jamf Connect Login to use the Microsoft identity platform (v2.0) endpoints for authentication.

For more information about the Microsoft identity platform (v2.0), see the following documentation from Microsoft:




The tenant ID in your organization to use for ROPG authentication.

Note: This key is required if you set the ROPGProvider key to "Azure_v2".




Specifies your OpenID Connect discovery endpoint. If using AD FS, this value is your AD FS domain combined with the following: "/adfs/.well-known/openid-configuration"


Note: This key is required if you set the ROPGProvider key to "Custom".




The redirect URI used by the created application in AD FS or Azure AD.

"" is recommended by default, but any valid URI value may be used as long as the configured value in Azure AD or AD FS matches the the value in your Jamf Connect Login configuration profile.




The client secret of your Jamf Connect application. Consider the following scenarios when configuring client secrets:

  • If you are not using a client secret for ROPG authentication, set this value to "NONE".

  • If you are using the same client secret for both ROPG and the authorization grant with Azure AD, do not set this key. Jamf Connect Login will use the secret set with the OIDCClientSecret key for both authentication and password verification.

  • If using a different client secret for each authentication process, set both OIDCClientSecret and ROPGClientSecret to their respective values.




An array of strings that contain error codes from Azure during an ROPG password verification, which should be interpreted as successful by Jamf Connect.

If using multifactor authentication (MFA) with Azure as a part of the Enrollment Customization feature in Jamf Pro, you may need to use this key to ensure Jamf Connect does not incorrectly interpret an MFA response as an error.

For possible error codes that may need to be configured in your environment, see the following documentation from Microsoft:






Related Information

For related information about Jamf Connect Login, see the following sections of this guide:

Copyright     Privacy Policy     Terms of Use     Security
© copyright 2002-2020 Jamf. All rights reserved.