-
-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "Restrictions" for configuring app-settings by MDM #197
Comments
This would require rebuilding the app each time settings are changed? Doesn't https://github.com/bk138/droidVNC-NG?tab=readme-ov-file#how-to-pre-seed-preferences do the same? |
In my opinion, the local file is a different scenario. The MDM is not able to put the json file in this directory. |
Good morning and thanks for your answer! If you get it to work, please leave a few notes here; might be interesting to others as well. |
Hi again, The goal is to make a mass deployable configuration which can be rolled out by MDM. The only way would be to setup the same access key on every device. There is not much saving here compared to setup the whole configuration by json-file. My next step is to request my MDM-vendor if there is a way to drop the json-File on the described location. I let you know the answer. |
It would be, but you can preseed the access key via the JSON, see the docs at https://github.com/bk138/droidVNC-NG?tab=readme-ov-file#how-to-pre-seed-preferences |
The MDM-vendor confirms that there is no way to put the json file by MDM. I think, configure the app by using managed settings is the only way that fits the needs of the described MDM-scenario. |
@stegl83 Are there any docs/examples/best-practices for the requested feature? Are you representing a company that would fund this? |
Hi, In Java it will be similar. After building the App and publishing to the store, the MDM will evaluate this new metadata and the configuration UI will look like this: restriction_values.xml:
app_restrictions.xml:
` |
For reading this settings in the app, you have to use RestrictionsManager-API. |
Thanks! Will go through this when I have so spare time. If you or your company need this in an expedited form, feel free to reach out to me via email. |
Hey @stegl83, I'm CEO and CTO of Nomid Tech, a MDM provider. |
@leandro-nomid @stegl83 Would happily merge a PR that's generic enough for all users, or, if that's not possible, detailed documentation of setting things up. |
When using Android Enterprise and a mobile device management (MDM), you can define in the appmanifest settings which can be configured by a MDM.
This XML-elements are called "restrictions".
see https://developer.android.com/reference/android/content/RestrictionsManager
An admin can create a policy to force the installation of the app and if restrictions are defined, the admin can additionally configure these settings. Interesting settings would be:
I think it is a good practise to support this managed settings feature.
The text was updated successfully, but these errors were encountered: