Open KuestenKeks opened 1 month ago
Same here. After switching back to 1.2.1 it's working again.
@KuestenKeks Delete the 1.3.0 version, download the 1.2.1 release from last year & install it. Should be working immed.
@KuestenKeks @jprusch Can you please tell me the mattermost server version and other details you can give me about the environment and error maybe.
Sure: Mattermost 9.8.0. Upgraded plugin to 1.3.0 and did an disconnect / connect to test. The new connect didn't work (See above. Exactly the same on our side). We checked the application permissions on the M$ 365 / Azure side: They were correct. Any user trying to connect got an authentication dialog eventually asking for an Azure admin confirmation. Even if this has been given while waiting in the dialog, that never got thru. Reverting to 1.2.1 fixed the issue immediately.
I can update again to 1.3.0 & enable all logs, if this is of any help.
I can update again to 1.3.0 & enable all logs, if this is of any help.
Thanks @jprusch that would be much appreciated.
Desktop logs are clean.
This is whats displayed:
Mattermost server log (only lines which contain "calen")
In contrast to the 1.2.1 plugin the connect message is shown opening the M$ connect dialog. With 1.2.1 this doesn't open, it's just connected.
thanks @jprusch! Version 1.2.1 is working just fine. It seems like the 1.3.0 release has also been removed in the meantime.
@Kshitij-Katiyar We're running the current ESR release of Mattermost: 9.5.5. Let me know if you need anything else.
Yes, I discussed with devs & we decided that it doesn't make sense to have a non-working release in the marketplace. I'll test the next release before it's heading to the marketplace.
This is the sequence of steps, when I try to connect the plugin to my M365 account:
I click on the bot message:
A window pops up where I can choose my M365 account. It says I'm already logged in ("Angemeldet"), probably because I've also installed and configured the Teams meeting plugin:
This message box is shown where it says that certain permissions are required, that need to be approved by an administrator. When I click on "Genehmigungsanforderung", administrators get an approval request:
I approve the permission request in the azure portal
I try again to connect the plugin to my M365 account, but I still get the same message box as in step 3, where I can create a new approval request despite that the previous one has already been approved.
That's how it played out yesterday. I thought maybe waiting a day would change something, but it's just the same today. I've configured the plugin as described in the documentation. The configuration was very similar to the MS Teams plugin, which works just fine. When connecting the Teams plugin with my M365 account, There was no permission approval needed, I did not get a message like I did here in step 3.
Kind regards!