Release Information > Version 2.3

New Features

Authentication via MS Azure AD

Use Case:

Authentication should also be possible via Azure Active Directory.

Implementation:

▪We have further developed the existing authentication tool. This extends the login option to include authentication via Azure AD.
You can find instructions on the steps in the Azure AD integration help article.

▪The development of the current authentication tool will not be continued and support for it will end on 31 March 2025.

▪We recommend installing and setting up the new tool as soon as possible.

Multi-factor Authentication

Use Case:

The Microsoft Azure Active Directory should be able to be used to utilise multi-factor authentication (MFA).

Implementation:

▪We have further developed the existing authentication tool. This extends the login option to include authentication via Azure AD
You can find instructions on the steps in the Azure AD integration help article.

▪The development of the current authentication tool will not be continued and support for it will end on 31 March 2025.

▪We recommend installing and setting up the new tool as soon as possible.

Extended properties for the BMS import

Use Case:

▪When importing AD persons, all data available for import should be imported into the bTS.

Implementation:

▪The following properties have been added to the import

•firstName

•lastName

▪The property ‘managerUserPrincipalName’ is currently not available from baramundi. As soon as this is available, we will add this property to the import.

Bug Fixes

▪Fixed an issue where a ticket was incorrectly set to the status ‘in progress’ even though the entry of a reason was cancelled in the self-service portal.

•A bug has been fixed where a script error occurred when copying a task workflow.

•The dark mode has been revised.