In order to leverage MANAGED SETTINGS, the following requirements and recommendations are provided below.
Network connectivity is mandatory to allow the licensing server to validate permission to apply customisations. If you do not need or wish to customise the app, working offline is fine. Get in touch for assistance.
The following endpoints are required for application functionality:
PING is the activation/licensing service. 2 through 9 are endpoints for push notification support on which configuration may be sent (note: no actual push notifications will show on devices, there's no current use case for it).
These endpoints are optional:
For wider Android Enterprise support, which includes the managed configuration function of MANAGED SETTINGS, access to Google Play, account services, and more, read up on the Android Enterprise Network Requirements.
Neither of these are mandatory, however links will fail with a warning.
MANAGED SETTINGS, the public version, requires a network connection to validate the application licence for licensed customisations. Given the obvious use case of kiosk and dedicated/single purpose deployments I appreciate this won't work for all organisations. Orgs looking for offline support have two options:
Get in touch via project-support@bayton.org to discuss.
Are you in need of further help, or would you like to raise a feature request? You can: