[cvs] [Wiki] changed: Project/ActiveSync

[Michael Rubinsky]

mrubinsk  Thu, 08 Apr 2010 16:46:29 -0400

Modified page: http://wiki.horde.org/Project/ActiveSync
New Revision:  1.40
Change log:  Remote wipe is functional

@@ -34,9 +34,17 @@
  </code>

  +++ What works

-Contacts and Calendar syncing is mostly working.
+Contacts and Calendar syncing is mostly working. Provisioning along  
with remote wipe is also working on devices that actually support it.  
No user interface yet exists for initiating a remote wipe, if you want  
to test this you need to:
+
+1. Open up the device's info file. This is in your state directory  
and is named info-{deviceidgoeshere}.
+2. Set the 'rwstatus' value from 0 to 2.
+3. Change the policykey to 0 (actually, any value other then the  
current policykey would work).
+4. Save the file
+
+The next time the device attempts to request a command other then  
PING or OPTIONS, it will be wiped. DO THIS AT YOUR OWN RISK!!!
+

  This code has been tested to some degree on the following devices:
  || Device || Version(s) || Provisioning || Notes ||
  || Android SDK Emulator|| 2.0.1 and 2.1 || Does NOT support  
provisioning and will NOT work with it set to //Force// or  
//Allow//.||Contacts only as the emulator does not have a native  
calendar application ||
@@ -61,10 +69,8 @@

  * Need to implement ghosted properties / SUPPORTED tag. Currently,  
each message that is sent from PIM -> Server is overwritten and  
replaced with only what the PIM sends. It's possible for some PIMS to  
ghost contact and calendar properties so that only the supplied tags  
are changed and missing, ghosted, properties are retained on the  
server.  When a PIM supports this, it sends a SUPPORTED tag with  
children representing the NON-ghosted properties. The absence of the  
SUPPORTED tag would indicate that any property not transmitted should  
be handled as a ghosted property.

  * Configurable heartbeat interval range: The protocol allows for  
rejecting heartbeat intervals that fall outside a specific range, and  
send back a suggested heartbeat interval to the client. This should be  
implemented as a configuration value.
-
-* Basic support for provisioning is already implemented, but support  
for remote wipe still needs work. Version 12 and higher also support a  
"local wipe" which automatically wipes the device when certain  
policies are violated such as maximum password attempts (see task  
below regarding versions).

  * Todo syncing: Neither the iPod/iPhone or Android have a native  
Todo application. !TouchDown does provide one, but backend support  
still needs to be added.

  * Implement more recent protocol version support - version 12 or  
maybe 12.1 (Exchange 2007??) should be fairly non-disruptive. Version  
12 would get us more atomic policy settings, local wipe rules, as well  
as the ability to send the policy settings to the client as the more  
compact wbxml. 14 (Exchange 2010?) would probably be lots more work as  
it does away with PING, using SYNC for waiting for changes instead.