Flyve MDM allows your company to maintain control of all mobile devices, whilst providing comprehensive protection and enhanced security for sensitive corporate data, via a centralized management console.
To get started, check out Flyve MDM website!
Web site to resolve flyve:// deeplinks
The project consist in static html files to display the information for enrollment, the most important folder is site.
The deeplink features three ways to display the information to execute the enrollment.
When the invitation is opened from the email account of the user, in the respective device to enroll, the email will display the deeplink with the information of the invitation encoded. Also the QR code image is attached.
After opening the link the MDM Agent will recognize it and start the enrollment.
The deeplink can also be opened in a computer's browser, in this case the deeplink will decode part of the information and display the Helpdesk information and the QR code, so the user can scan it from the MDM Agent and make the enrollment.
In case the invitation is opened with the browser of the device, it will display a button that contains the deeplink so the MDM Agent can recognize it and start the enrollment.
If the App isn't installed, the deeplink will redirect to the Play Store to download the MDM Agent in order to proceed with the enrollment.
| LTS | Bleeding Edge |
|---|---|
 |
 |
To host your own instance of Flyve MDM Deeplink microservice, just follow these steps:
- Clone the project in your server directory
- Add your settings in the
site/config.example.js file, then rename it tosite/config.js- defaultLocation: the address to redirect in case there is no data to process by the deeplink
- bugsnagApiKey: optional, the apikey to your bugsnag
- deeplinkBase: the customroute for your app, for example:
flyve://register - androidDefaultLink: the route of your application in the market place
- iosDefaultLink: the route of your application in the apple store
- Add your deeplink route in Flyve MDM settings in GLPI
- Go to Flyve MDM > General configuration > Invitation deeplink
- Write
http://my-site/deeplink/site/
In order to provide transparency on our release cycle and to maintain backward compatibility, Flyve MDM is maintained under the Semantic Versioning guidelines. We are committed to following and complying with the rules, the best we can.
Release announcement posts on the official Teclib' blog contain summaries of the most noteworthy changes made in each release.
For notices about major changes and general discussion of Flyve MDM development, subscribe to the /r/FlyveMDM subreddit. You can also chat with us via IRC in #flyve-mdm on freenode or @flyvemdm on Telegram.
The Flyve MDM and GLPI Network services are available through our Partner's Network. We provide special training, bug fixes with editor subscription, contributions for new features, and more.
Obtain a personalized service experience, associated with benefits and opportunities.
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the Issues Dashboard.