Closed cmseal closed 4 months ago
@cmseal I tried reproducing the above issue on my system but was not able to. I was able to run the /zoom settings
command and disable the PMI setting, and the new meetings generated were generated using a random ID.
Can you please confirm whether you were not able to run the slash command /zoom settings
or the command was not functioning properly according to the value set?
Also, can you please state the Mattermost server version and Zoom plugin version you are using?
cc: @pvev
Hi @ayusht2810
Per my first screenshot, when I try to run /zoom settings
, it just tells me which commands are available (start, connect, disconnect), so it behaves as if it's not even a valid command.
MM server is v9.5.3 and Zoom plugin is v1.6.2
If you require any further information, please do let me know. I was wondering if it was permissions scope related with the Zoom OAuth setup, but we've got the scopes for account-level as per the recent update to the README.
@cmseal The plugin v1.6.2
does not support the /zoom settings
command. The command was introduced in the latest release https://github.com/mattermost/mattermost-plugin-zoom/releases/tag/v1.7.0. If you want to have that functionality working, you need to update the plugin version to v1.7.0
. Please let me know if you have any other concerns regarding this.
@ayusht2810 Thanks for clarifying - we're using the version that the MM app marketplace recommends, which is 1.6.2 and doesn't suggest or notify there's a newer version available.
@cmseal Thanks for understanding. We are already working on releasing the new version for the plugin on marketplace.
The
/zoom settings
command is not possible (possibly due to account-level OAuth). Likewise meaning that only personal "per user" meeting IDs are used each time.Is there a setting or permission required to allow unique meetings each time? likewise, do they persist or expire after a period of time?