[Tickets #11638] Re: ActiveSync :: The Autodiscover URL must be configurable, not extracted from the email address performing the query.

bugs at horde.org bugs at horde.org
Mon Nov 5 15:22:15 UTC 2012


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

Ticket-URL: http://bugs.horde.org/ticket/11638
------------------------------------------------------------------------------
  Ticket           | 11638
  Aktualisiert Von | torben at dannhauer.info
  Zusammenfassung  | ActiveSync :: The Autodiscover URL must be configurable,
                   | not extracted from the email address performing the
                   | query.
  Warteschlange    | Horde Framework Packages
  Version          | Git master
  Typ              | Enhancement
  Status           | Accepted
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       | Michael Rubinsky
------------------------------------------------------------------------------


torben at dannhauer.info (2012-11-05 15:22) hat geschrieben:

>> If you have a single horde installation serving a couple of domains,
>> you oftne have only one SSL certificate covering the domain of your
>> horde installation, not of all virtual domains the horde installation
>> serves.
>>
>> Because the AutoDiscover feature is usually performed via SSL and
>> mosts clients quit autodiscovery if the find a untrusted or invalid
>> SSL certificate, it is mandatory to return an ActiveSync URL covered
>> with that SSL certificate, not with URL derived from the email Domain.
>
> The host is NOT directly calculated on ther server from the email  
> address provided by the user/client. It's parsed out of the result  
> of Horde::url(), which returns a URL based on $conf['server']['name'].
>
> Are you using virtual-domain specific configuration files?  If so,  
> that might explain why this is happening since the *client* uses the  
> email address to determine which server to query for the  
> Autodiscovery.
>
> Telling ActiveSync to use the one domain for all activesync requests  
> will cause your custom domain specific configuration files to be  
> ignored.
>
> Instead of adding this as a configuration option, I'm going to add a  
> new hook. I've had various hooks planned for autodiscover but were  
> pretty low priority for me.

Hmm, that sounds horde has already the right behaviour I need. Maybe  
I've mixed something up, I was hunting several horde problems in the  
last days.

I'll check this again after work and will comment this bug again.

Yeah hooks sounds great, this would allow to modify the autodiscover  
behavior without adding lots of new options to the configuration.

Torben





More information about the bugs mailing list