If this attribute cannot be verified, the user will be asked to select a local account to associate with the user’s Okta account. With the Migrate and DenyLocal preference keys, all subsequent sign-ins will be authenticated to Okta, and then the system verifies if the user record has an “OktaUser” attribute. This way the user can sign in to the system as their Okta username.Īdditionally, Okta can migrate users from local accounts to accounts associated with an Okta identity. At this point Jamf Connect Login will synchronize the password to the Okta password, and then add the Okta username as an alias to the local account. To migrate an account, the user must provide the existing local password. If a user's Okta username does not match any local account, the user will be given the option to create or migrate a local account. Once successfully entered, Jamf Connect Login will use the current local password and the current Okta password to sync the account to the current Okta password. If a user's Okta username matches a local username but the passwords do not match, the user will be prompted to enter their current local password. If a user's Okta username and password match a local username and password, the account is considered migrated. Consider the following user migration scenarios: Jamf Connect Login does this by forcing the user to sign in via Okta, and then attempts to match the user with an existing local account. 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 Okta identity. Used with DenyLocal to force authentication to Okta first, but then fallback to local auth if Okta is unavailable.Īllows local accounts to be migrated to Okta-based accounts. Note: Maintaining your license key in a separate configuration profile provided by your account manager is recommended. Configuring Preferences with the Command Line.Configuring File Shares with Jamf Connect Verify.Integrating Kerberos with Jamf Connect Sync.Configuring File Shares with Jamf Connect Sync.Configuring Jamf Connect Login with PingFederate.Configuring Jamf Connect Login with OneLogin.Configuring Jamf Connect Login with Okta.Configuring Jamf Connect Login with Microsoft Azure AD.Configuring Jamf Connect Login with IBM Cloud Identity.Configuring Jamf Connect Login with Google ID.General Requirements and IdP Compatibility.Both applications have different preference domains as well, so the configurations do not cross. While running them at the same time on the same Mac might be a bit strange, both applications would run independently and not interfere with the other. It’s perfectly feasible to run both NoMAD and Jamf Connect in an organziation. If you still are using mobile accounts on your AD-bound Macs and have Okta synchronizing with AD please talk to us about the best workflow for that situation. Jamf Connect is designed to work with local-only accounts when keeping the password synchronized. Jamf Connect can get Kerberos tickets, but NoMAD can’t get Okta tokens.NoMAD has no support currently, or planned, for multi-factor authentication. Jamf Connect supports multi-factor authentication requirements.All authentication is done via Okta’s publicly available endpoints. Users never need to actually connect to the AD domain.While NoMAD and Jamf Connect can do some similar functions, the choice between the two primarily comes down to using Okta (or other identity providers) for authentication with Jamf Connect or using AD for authentication with NoMAD.įor organizations deploying Macs to single users that are often off of the AD domain, Jamf Connect offers a number of features that allow for a smoother workflow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |