Summary | EAS provisioning | No device admin | Wipe only removes EAS Account |
Queue | Synchronization |
Queue Version | FRAMEWORK_5_2 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | samuel.wolf (at) wolf-maschinenbau (dot) de |
Created | 06/07/2020 (1851 days ago) |
Due | |
Updated | 06/14/2020 (1844 days ago) |
Assigned | 06/07/2020 (1851 days ago) |
Resolved | 06/14/2020 (1844 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Assigned to Michael Rubinsky
State ⇒ Not A Bug
App, there is no question to approv.
the entire device is actually determined by the application and
system itself. For instance, I think the stock android app normally
wipes the entire device, while an application like "Nine" will only
wipe the EAS account data. There's nothing in the provisioning
protocol that specifies the "level" of wipe to do. It's just a
command to "wipe".
this is what you mean?
https://techcommunity.microsoft.com/t5/intune-customer-success/decreasing-support-for-android-device-administrator/ba-p/1441935#
State ⇒ Feedback
that account has to be added as a Device Admin App, or do you mean
that if you setup Horde's ActiveSync to not *require* provisioning the
device is not able to be wiped?
Unless I'm mistaken, the ability of an application to remote wipe the
entire device is actually determined by the application and system
itself. For instance, I think the stock android app normally wipes the
entire device, while an application like "Nine" will only wipe the EAS
account data. There's nothing in the provisioning protocol that
specifies the "level" of wipe to do. It's just a command to "wipe".
Priority ⇒ 1. Low
New Attachment: Permission_EAS.png
Patch ⇒ No
Milestone ⇒
Summary ⇒ EAS provisioning | No device admin | Wipe only removes EAS Account
Type ⇒ Bug
State ⇒ Unconfirmed
Queue ⇒ Synchronization
"Device admin apps".
If the device is now wiped over Horde, only the EAS account will
removed but the device not wiped.
This works before, maybe it's a provisioning problem?
Or something change in Android 10?
Tested with Nokia 6.2 and 7.2 Android 10 Patchlevel May 2020
libapache2-mod-php7.3 7.3.14-1~deb10u1
Horde_Core 2.31.13 stable
Horde_ActiveSync 2.41.3 stable