Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
The current DOMI of Zoom and other Online Meeting solutions will not or just hardly be useable in enterprise network situations.
Most of all customers use a proxy to secure their infrastructure. Most of the Proxy configuration needs authentication and in addition many customers use Citrix Terminal server implementations of the Notes (12.0.2) Client.
As the Location document Proxy setup works fine for the common Notes UI functions, it did not work for DOMI.
Sorry, this solution is not suitable. Administrators may set up general proxy OS Environment variables by a Windows Domain Group Policy but never would set up username / password in clear text into the OS user context Environment variables.
Also the user is not able and not permitted to configure this.
Even though this will not work, because the authentication against the Proxy service must be done with the frequently changing Windows AD credentials in most cases.
DOMI can not be configured or used in this context.
I got not only one customers who like to use Zoom with DOMI but fail already in the Zoom Token validation.