Does Jamf Pro 10.17's LDAP features make Jamf Connect Obsolete?

[TechSpecialist]

Hi all,

Our organisation has purchased licenses for Jamf Connect, so we can avoid using an on-prem directory service to authenticate the users while logging in to their Macs.

Am I right to think that for this purpose Jamf Connect has become obsolete (for us) as we can now use LDAP in the new Jamf Pro 10.17 to authenticate users into their iMacs?

Any arguments to maintain working with Jamf Connect?

[ablend]

I could be wrong, but in the release notes I read it as you have the ability to use an LDAP server for the DEP Enrollment authentication stage, which ties the proper user in LDAP to the device within Jamf Pro. This does not create a local account on the Mac with the user information that was provided. For that functionality, you would need Jamf Connect. Without Jamf Connect, the user would be presented with the Setup Assistant to create an account.

[mainelysteve]

@ablend If you have authentication turned on as well as a user payload in your pre-stage it will create a local account based on the credentials entered earlier. The account created on the Mac will be on its own island after that though. That's where software like jamf Connect or even NoMAD come in to maintain the sync between the two.

[ablend]

@mainelysteve Interesting new feature that I'll have to test out. Thanks for the clarification!