Hey everyone,
We’re currently using another UEM solution for our Android fleet, and one thing we’ve been struggling with is auto-login for an enterprise app.
The app requires two values during installation:
Our current UEM can’t inject these values the way we want. Before we consider switching, does anyone know if Hexnode supports passing both serial number and a custom token through app configurations?
19 Views
Hey @noah-blake ,
Yes, this is actually a very common setup for enterprise apps that rely on automatic enrollment or silent authentication. If your app supports managed app configurations, Hexnode can definitely pass device information into a JSON payload.
For the serial number, Hexnode provides a wildcard called %serialnumber%. When you push the app, Hexnode automatically replaces that wildcard with the actual hardware serial number of the device. Once that’s confirmed, Hexnode can deliver whatever fields the app expects.
Building on @stevenhere point, the application token is handled a bit differently. Since it’s not a device attribute, it cannot be pulled or generated automatically. But if the app provides a config key for it (something like “app_token”, “auth_key”, or “registration_token”), you can still include it manually inside the JSON.
If you’re setting this up for the first time, the Hexnode help article explains the full process of using App Configurations for Android, including JSON mode: How to configure Application Configuration for Android devices.
This is great to know, I’ll get in touch with the Hexnode support team to understand how this would work for our app. Thanks a lot for the pointers, everyone!
Don't have an account? Sign up
