access Webex site from client side

[bbodenmiller]

Many Mattermost servers are not allowed to access the outside internet by default. This plugin should support this and access Webex site from client side.

[cpoile]

@bbodenmiller This turns out to be how connections to webex work currently. The plugin generates a link and posts it in a message, and when a user clicks on the link in a message they connect directly to the webex system -- there's no traffic through the Mattermost instance during/after the link click.

Please let me know if I'm misunderstanding the issue?

[bbodenmiller]

I get that but is the sever or client connecting to Webex to generate the link in the first place? My sever isn't able to access any content on *.Webex.com.

…

On Thu, Jan 30, 2020, 6:31 AM Christopher Poile ***@***.***> wrote: @bbodenmiller <https://github.com/bbodenmiller> This turns out to be how connections to webex work currently. The plugin generates a link and posts it in a message, and when a user clicks on the link in a message they connect directly to the webex system -- there's no traffic through the Mattermost instance during/after the link click. Please let me know if I'm misunderstanding the issue? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJDGTF2NYBNAAQXIS34DZDRALQCTANCNFSM4KLTCKZQ> .

[levb]

@bbodenmiller ACK. Historically, we focused on server-side and/or server-centric plugins; largely to enable functionality on mobile.

However, there's nothing really, at least in theory, preventing us from creating 100%-webapp plugins (well, serving them from the server). We should consider.

[bbodenmiller]

@levb right, I've found the Mattermost move towards more sever side connections when client side would be possible problematic. In security sensitive environments server connections to outside internet are more restricted (blocked entirely in many cases) than client side connections to outside internet.

[cpoile]

@levb We could have a back-up webex-client code on the front end. It would query the webex server for the room url given the meeting starter's preferred setting. I think it can be a HW.

[levb]

It is my understanding that the client was already not restricted and has no issue connecting to WebEx; the server (plugin!) must use a proxy though. Client can be configured separately anyway.

[cpoile]

You're right, the client can do the connection, but the client will need to respect the meeting starter's preferred way to find their meeting room URL (roomId, username/webexId, or email). Then the client can query the Webex server to get that URL.

We need to include that info in the meeting post (as props), then the client needs to have all the webex xml request settings to make the request (can be found in the server/webex package).