[Tickets #14727] Re: Getting back invalid ActiveSync response upon Provision request

noreply at bugs.horde.org noreply at bugs.horde.org
Mon Nov 13 08:55:11 UTC 2017


BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14727
------------------------------------------------------------------------------
  Ticket           | 14727
  Aktualisiert Von | john.bieling at gmx.de
  Zusammenfassung  | Getting back invalid ActiveSync response upon Provision
                   | request
  Warteschlange    | Synchronization
  Version          | FRAMEWORK_5_2
  Typ              | Bug
  Status           | Not A Bug
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       | Michael Rubinsky
------------------------------------------------------------------------------


john.bieling at gmx.de (2017-11-13 08:55) hat geschrieben:

Thanks for pointing that out. From the client side, I now skip  
provisioning, if I get back such a response.

If I am allowed to ask here: Should the client disable provisioning  
altogether (and never ask for a policy key again) or should it  
continue to ask for a policy key on each request and skip if none is  
returned?

This is why I ask: Horde sends "provision" with its OPTION response,  
so the administrator does want to provision the devices,but does not  
provide a policy for each. Now if at some later time he DOES provide  
one for a specific device, the client will never catch it, because it  
has disabled provision.

What is the correct way to handle this? What do you as the developer  
have in mind, when you send that response? I fail to find a proper  
answer in the active sync documentation...

Thanks for your time
John

> Status 2 means that provisioning is not required for your server  
> configuration.
>
> This is a support question, not a bug report.
>
> Please use the mailing lists to ask for support.
>
> http://www.horde.org/mail/ contains a list of all available mailing lists.






More information about the bugs mailing list