Qué está cambiando

Google Meet hardware devices can now trust HTTPS certificates signed by a private certificate authority (CA). This simplifies the process of setting up and managing third-party user control interfaces (UCIs), especially in high impact meeting spaces with systems like Q-SYS.

Previously, you had to get certificates signed by a public CA to enable Google Meet hardware touch controllers to load third-party UCIs. This process was often time-consuming and expensive, and required frequent renewals.

Now, Google Meet hardware devices can trust certificates signed by a private certificate authority, enabling them to securely load a third-party room control system’s UCI. This gives you more control over your network security and eliminates the costs and complexities associated with public certificate signing.

Para empezar

• Admins: Visite el Centro de ayuda para obtener más información sobre setting up an HTTPS certificate authority y setting up a 3rd-party control system. 

Admin console >Menu > Devices > Networks > Certificates

• Usuarios finales: There is no end user impact or action required.

Ritmo de implantación

• Ámbitos de liberación rápida y liberación programada: Gradual rollout (up to 15 days for feature visibility)  starting on January 23, 2025

Disponibilidad

• Disponible para todos los clientes de Google Workspace con dispositivos de hardware Google Meet
• Please note that Android devices aren’t supported yet.

Recursos

• Google Workspace Admin Help: Set up an HTTPS certificate authority
• Google Workspace Admin Help: Integrate third-party control systems