[horde] Can't authenticate with Activesync

[Michael Wisniewski]

Quoting Michael Wisniewski <wisniewski at mwiz.org>:

> I've been battling getting Activesync working, and I believe I broke  
> it again.  I had it working, but then I deleted my device and tried  
> to recreate it, and can't.
>
> On my android phone, my device says invalid password when trying to  
> do a manual configuration.  If I try to visit the web page  
> <domain>/autodiscover/autodiscover.xml, I get a pop that says "Horde  
> ActiveSync", but my username and password do not work.
>
> In my authentication backend, I have "let a horde application handle  
> authentication" using imp.  I can get into imp just fine and  
> everything works in there through the web interface.  It just seems  
> like activesync doesn't want to authenticate.
>
> In my apache config, I have...
>
> Alias /Microsoft-Server-ActiveSync /var/www/webmail/rpc.php
> Alias /autodiscover/autodiscover.xml /var/www/webmail/rpc.php
> RewriteRule .* - [E=HTTP_MS_ASPROTOCOLVERSION:%{HTTP:Ms-Asprotocolversion}]
> RewriteRule .* - [E=HTTP_X_MS_POLICYKEY:%{HTTP:X-Ms-Policykey}]
> RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
>
>
> Thank you in advanced for help.
> mike
>

What a huge PITA.  I couldn't figure out what was going on with this  
thing.  I ended up wiping my whole install (/var/www/webmail)  
directory ALONG with the MySQL database.  Still doing the same exact  
thing.  I then tried to turn the debug log on for activesync, and  
realized it logged per device in a directory and not to a file.  Saw  
it showed this...

2013-04-01T20:46:00-05:00 INFO: [23990]  
Horde_Core_ActiveSync_Driver::authenticate() attempt for wisniewski
2013-04-01T20:46:00-05:00 DEBUG: Access denied for user wisniewski per  
policy settings.

I then remembered I tried to setup provisioning for my device but  
removed that policy.  I went into the configuration and re-enabled  
provisioning, and everything is now working again.

So, I have absolutely no clue where once you set provisioning you  
can't go back exists, but it does.  I thought removing everything on  
the server would also wipe any changes I did, but I guess provisioning  
stuck.  What a pain, but at least I got it working.