proposals
proposals copied to clipboard
WICG
Managed configuration API
Introduction
On devices that are managed by an organization, there is a need to thoroughly set up the environment for the web applications before use. This API provides a way for web applications to access administrator-provided configuration.
This API is proposed to be added under new navigator.device namespace, which will be available to highly-trusted applications only.
Feedback
I welcome feedback in this thread, but encourage you to file bugs against the Explainer.
Thanks for putting this together. This API is exceptionally important for centrally managed Chrome/PWA deployments, specifically in the K-12 education space. It's critical to have granular controls over security and account settings that prevent / allow students from changing their screen names, joining meetings outside of their domain, hosting unauthorized meetings, and additional trust and safety based issues. Overall, web applications require the same control, configuration, and treatment as native applications to avoid feature and security regression.
This API is required by Citrix in order to have a mechanism to push Enterprise policies configured by the administrator for the PWA app that can be read with a schema on any managed endpoint machine(ChromeOS , Win, Mac etc).
This API is needed for the DRC PWA to enable the device management console in Google Admin to provision the application to managed devices en masse w/ pre-determined configuration keys that enroll the device to the appropriate configuration in DRC's management system. We are also able to provision a unique toolkit URL that directs the application to a unique client-specific backend, required by some clients.
This api is also vital to our efforts to transition to PWA for thousands of production kiosks-mode devices in an enterprise environment. We orchestrate as much configuration of these devices programmatically as we can, but it needs to be in a secure and robust way.
@reillyeon - Do you know the current status of this proposal?
This API has been fully shipped in M91 and already used by enterprise customers. Should I close this thread, or you have a more specific question. Thanks for any guidance, concerning this was the first Web API which we worked on.