Hello Jamf Nation!
We are excited to announce that the Jamf Connect 2.13.0 beta is open for enrollment. Important changes of note:
If your identity provider is Microsoft Azure, upcoming changes to Microsoft Authentication Library (MSAL) require changes in your Jamf Connect configuration. Existing applications remain functional, but in December 2022 Microsoft will discontinue security updates for Azure Active Directory Authentication Library (ADAL), deprecating the use of common endpoints. To align with these changes in Jamf Connect, you must include organization-specific tenant information for your registered authentication applications in your configuration. For more information about these changes, see https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-migration
This beta enables the use of these updated endpoints as the default authentication scheme for Connect, when configurations include the required details. For configurations without organization tenant specific information, authentication will remain functional. To support these changes, Jamf Connect Configuration now requires the inclusion of an Azure Active Directory Tenant ID – which is available on your Azure Active Directory Overview portal.
Detailed information is available in the release notes for enrolled beta testers.
How to join the beta :
Log in to Jamf Account to enroll in the Beta Program, available under Product Feedback at account.jamf.com. After enrollment approval you will see a link to the Beta Forum. There's a short delay while you are approved for access to the forums. If you have any questions please email email@example.com. The beta program is operated under non-disclosure, so please do not share any information regarding your testing on any public forum, including the non-beta sections of Jamf Nation. Please use the Jamf Nation beta discussion area to provide feedback or ask questions about the beta.
Thank you to all those who participate in the program - we appreciate your time and feedback.
The Connect team