With the release of version 2.15, the authentication mechanism for Microsoft Office 365 has been updated to utilize the latest API interfaces. This change introduces a modification to the user session management.
- Session-Based Login:
User login credentials are now valid for the duration of a single application session only. If you refresh the application page or the browser, the current session is terminated and you will be required to re-authenticate. - Account Switching:
To switch between different Microsoft 365 accounts, you now have to perform a full refresh of the application or restart the browser. The previous method of switching accounts within the same session is no longer supported.
Note:
It might be required that your Microsoft Office 365 administrator has to re-authorize our application. This is necessary because the application ID has changed. This is therefore a one-off action that must be carried out by the Office 365 Administrator within your own organisation for all individual pCon.basket users who request (need) authorisation for working with Office 365 in pCon.basket!
Normally, the Office 365 admin gets a request when the user requests access and then he get a link to the app list, that he/she can click on to to grant access again. A document (in English) has been added to the appendix of this article with an example of how to authorize an app in Office 365.
You can read the above in chapter 5 of the accompanying release document.