Jamf Connect 2.35 bug

29 views

Skip to first unread message

Marlon Yu

unread,

May 28, 2024, 10:28:43 PMMay 28

to Techies for schools

Hi,

Just a heads up for those using Jamf Connect and using the ShortName property … have discovered and reported yesterday to Jamf that passing the OnPremisessAMAccountname attribute to Jamf Connect as the attribute to use for the ShortName property works with 2.34 but not with the newly released 2.35 version. They have just confirmed it is a PI (not yet listed in their Known Issues page) so you might want to hold off on upgrading or disable the auto upgrade option.

If you are like us who have a different SSO login format (john....@domain.com) from their local AD logins (smi...@domain.local), you may end up with users unable to get to the local resources because Jamf Connect will pass on john.smith instead of smithj which your AD DC will obviously not know anything about.

Although we’re using Entra ID, I suspect it will affect Okta as well, as the bug appears to be that Jamf Connect does not pass on the value it receives in the token to ShortName.

Marlon

*** RANGITOTO COLLEGE EMAIL DISCLAIMER ***

The contents of this email and any attachments are confidential and may be legally privileged. If you are not the intended recipient please advise the sender immediately and delete the email and attachments. Any use, dissemination, reproduction or distribution of this email and any attachments by anyone other than the intended recipient is prohibited.