Note! The information below only applies if you are using Microsoft 365/Exchange Online! On-premises Exchange, Google Workspace and IBM Domino are not affected.
Table of contents
- The ERM Bridge beta
- ERM Bridge beta install instructions
Microsoft is retiring support for Basic Authentication
In March 2018, Microsoft announced that starting October 13, 2020, Exchange Online will no longer support basic authentication for a number of protocols, including EWS. EWS is used by some Evoko products to connect to Exchange booking system backends.
Since then, the retirement date for basic authentication over EWS has been moved several times. On September 24th, 2021, Microsoft announced that come October 1st, 2022, basic authentication will be permanently disabled for all tenants regardless of usage, with no option to opt-out.
What the September 2021 statement also says is that starting early 2022, Microsoft will temporarily disable basic authentication for random Microsoft 365 tenants for 24-48 hours.
Please see the September 2021 update from Microsoft here: Basic Authentication and Exchange Online – September 2021 Update - Microsoft Tech Community.
This change will affect some Evoko products that can use basic authentication with EWS.
Which Evoko products might be affected by this, and how?
The Evoko Naso, our cloud-based room booking system introduced in 2020 is not using basic authentication, so it is not at all affected by this change. Read more about the Evoko Naso on our website.
The Evoko Liso, introduced in 2017, uses EWS, but is compatible with modern authentication (oAuth) since Evoko Home version 2.2, and since version 2.3 it is compatible with the current oAuth enrollment process. This means that if you are using the Liso with Evoko Home v2.3 or newer and you are currently using basic authentication, all you have to do is to follow the instructions in the Change from basic to modern authentication in Evoko Home support document. If you are on an older version of Evoko Home, you can find update instructions here or submit a support request and we will gladly assist with getting your system up-to-date. Read more about the Evoko Liso on our website.
The Evoko Room Manager (ERM1001), introduced in 2009, uses basic authentication over EWS to connect to Exchange Online. Unfortunately, because of hardware limitations, the Room Manager as a standalone product will never be able to use modern authentication (oAuth).
I'm using the Evoko Room Manager - what do I do now?
For the Evoko Room Manager, there are currently two solutions available:
- The ERM Bridge beta is a server solution that acts as a bridge between the Evoko Room Manager and Evoko Home. With this solution, authentication is handled by Evoko Home instead of the Room Manager. Currently the ERM Bridge beta is in open beta. Read more about the ERM Bridge beta below.
- Talk to your Evoko sales person about replacing your Room Managers with the more modern Evoko Liso system, which is a modern all-in-one room booking system with smartphone app support and on-premise data storage, or our latest cloud-based product, the Evoko Naso, which also supports desk booking, visitor management, catering and has built-in contact tracing functionality.
Please don't hesitate to contact us with any questions you might have about either of the above options.
The ERM Bridge beta
What is the ERM Bridge beta?
The ERM Bridge beta is a client-server solution that connects the Evoko Room Manager to Evoko Home and thus makes the Evoko Room Manager compatible with any booking system supported by Evoko Home, including Microsoft 365 with modern authentication.
This is achieved by installing an intermediate server that acts as a bridge between the Evoko Room Manager and Evoko Home.
The main benefits of integrating the Evoko Room Manager into Evoko Home are:
- Centralized management even with mixed environments (Liso/Room Manager)
- Simpler booking system configuration since it only needs to be configured for Evoko Home.
- Better support for newer ciphers and technologies (including support for Microsoft 365 oAuth).
Drawbacks and limitations
There are also a few drawbacks:
- Beta software, should not be considered bug-free.
- Based on Internet Information Services - not compatible with Linux.
- Integration requires additional software and setup.
- Not currently possible to end meetings early from the Room Manager screen.
- Some Evoko Home settings need to be changed for the integration to work.
What are the requirements for ERM Bridge beta?
- A test environment. We strongly advise against using the ERM Bridge beta in a production environment. It should not be considered bug-free.
- A Windows Server with IIS
- An Evoko Home server with Evoko Home version 2.3 or above that the ERM Bridge beta can connect to. Evoko Home and the ERM Bridge beta do not have to reside on the same machine.
- The Room Manager application will need to be manually replaced on every Room Manager device.
ERM Bridge beta install instructions
Here are the instructions on how to integrate the Evoko Room Manager in Evoko Home using the ERM Bridge beta. After completing this procedure, your Room Managers will no longer be managed by Evoko Control Panel.
Important! Please read through this document in its entirety before starting and contact Evoko support if you have any questions.
About beta software: The ERM Bridge beta is beta software and as such it should not be considered bug free. We are doing our best to offer first class support for ERM Bridge beta, but you might run into issues that will take a long time to resolve and currently we do not recommend running the ERM Bridge beta in a production environment. If you have any questions, please contact Evoko support.
Server Setup - WebAPI application
- Evoko Home v2.2 or later needs to be installed and configured. For setup instructions, please see Evoko Liso / Getting started
- Download Evoko Room Manager Bridge beta from https://www.evoko.se/downloads/
(Select Downloads for Evoko Room Manager --> Evoko Room Manager Bridge)
- In Windows, open "Turn Windows features on or off" or "Server manager" depending on operating system version.
- If going through Server Manager, open "Add roles and features wizard".
- Enable Internet Information Services, then enable the following.:
- All options under World Wide Web Services\Application Development Features
- All options under World Wide Web Services\Common HTTP Features.
- Security\Windows Authentication
If using the "Add Roles and features" wizard you will find the above options under "Role Services" after selecting IIS.
- Click OK to enable the features, then let Windows Update download the necessary files and finally reboot the server if prompted.
- Run the setup.exe located in the Integration subfolder of the ERM Integration.
- After install has finished successfully, reboot if needed, then open Internet Information Services (IIS) Manager.
- Navigate to Sites -> Default Web Site -> EvokoWebAPI and click Edit Permissions.
- Go to the Security tab, click Edit, select IIS_IUSRS and click Full Control. Then click OK on the two dialog boxes.
- Restart IIS by clicking on the server name in the top left corner and selecting Restart under the Manage Server menu.
- Open a web browser and open http://[IP]/EvokoWebAPI, where [IP] is the ip of the server.
- Log in using EvokoAdmin and Password123.
- Under EH end point, enter the Evoko Home server IP and port, for example 192.168.1.108:3002
Important! Only enter IP:PORT! Do not enter protocol, slashes, or path.
- Open Evoko Home, go to global settings and copy the default API token, then paste it in the "Set MongoDB User details" tab in EvokoWebAPI.
This concludes the ERM WebAPI Endpoint configuration.
Evoko Home settings
In Evoko Home, the following settings need to be changed for the rooms that are going to be used with Room Managers.
- Go to Rooms -> Settings and select the rooms that are going to have Room Managers assigned to them. Click Edit Settings.
- Under booking settings, make sure everything is enabled except for Delete Future Meeting and Modify Future Meeting as the Room Manager does not currently support these features. Also disable all authentication settings as shown in the screenshot below.
Evoko Room Manager setup
This section will tell you how to configure the Room Manager for use with Evoko Home. Please note that after performing the steps below, your Room Manager will need a factory reset and reconfiguration if you would want to go back to using Evoko Control Panel.
Preparation: Copy the MeetingManagementSetup.CAB file to a FAT-formatted USB stick.
- On the Room Manager, log on using an admin PIN and select Exit Application.
- Open My Device on the desktop by double tapping it.
- Open ResidentFlash, select the MeetingManagementSetup folder, tap the File menu and select Delete. Click yes when asked if you are sure you want to delete the folder and any files in it.
- Insert the USB stick with the MeetingManagementSetup.CAB file, open My Device on the Room Manager and navigate to "Hard Disk".
- Copy the installer to the desktop by selecting the MeetingManagementSetup.CAB file, then tap the Edit menu and select Copy. Navigate to the Windows\Desktop folder, tap the Edit menu and select paste. You can also paste it by closing the file explorer and long pressing on the desktop and selecting paste on the popup menu.
- Run the installer from the desktop by double tapping the icon.
- Change install location to \ResidentFlash and tap OK to install the software.
- Start the new Room Manager software by double tapping the icon.
- When prompted, select protocol and enter the IP address to the WebAPI using the touch screen, then tap the green check mark.
- The Room Manager will connect to the WebAPI and download the configuration which will take a few minutes. The Room Manager will restart and you will be presented with the Select a Room screen.
- Select the room this Room Manager should be assigned to.