on 04-02-2019 2:43 PM
We are using Afaria (7.00.20333.0 SP32 1812) and it works fine with any mobile device and Android version except the new Android 9.0 release.
While we try to enrol a new device using tinyURL code the following message pops-up on the screen:Enrollment failed.
Can you please let me know if anyone else was reporting this issue and if you could try to help us resolve the problem?
Other details that might be useful:
SAP Mobile Secure for Android 6.60.22110 SP32 1812 release
This image shows the problem that we are facing. Now, after we insert the enrollment code in our android devices, the Mobile Secure App can’t reach the address of the XNET server. The strange thing is that we never modify this configuration in our Afaria Cloud enrollment Policy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lukasz,
I am facing the same problem with my devices. I already open an incident for SAP support, but until now I am not able to register new devices in Mobile Secure (Afaria Cloud) anymore.
The hint sent by Atsushi Asano didn't work for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lukasz,
I made a mistake.
Android 9 and later, Google has restricted the use of HTTP. (HTTPS is now required by default)
This issue is that, while the enrollment server address in the enrollment code policy has been updated to use HTTPS, the enrollment code still points to a stale HTTP address.
You'll need to regenerate the enrollment code (tinyurl) so that it's updated to use the new HTTPS address.
BTW, we are unable update the enrollment code location automatically as it's not our service.
Thanks,
Atsushi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Atsushi,
no. It's a brand new device with Android 9. And we are still unable to use it with SAP mobile secure asit throws the same error message every single time. Please check the very first post for details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lukasz,
Were your devices updated to Android 9.0 whilst still being enrolled?
In this case, the previous device would need to be removed from admin as I believe the payload may vary between Android previous version and 9.0.
Thanks,
Atsushi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, is there any update on the above? We're still unable to use Afaria with any Android 9 device.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.