6.0.0-beta1
7/7/25

[#12731] inconsistent authentication id usage within the activesync
Summary inconsistent authentication id usage within the activesync
Queue Horde Framework Packages
Queue Version Git master
Type Bug
State Resolved
Priority 1. Low
Owners mrubinsk (at) horde (dot) org
Requester leena.heino (at) uta (dot) fi
Created 10/02/2013 (4296 days ago)
Due
Updated 10/02/2013 (4296 days ago)
Assigned 10/02/2013 (4296 days ago)
Resolved 10/02/2013 (4296 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
10/02/2013 04:56:55 PM Michael Rubinsky Comment #4
State ⇒ Resolved
Reply to this comment
Pretty sure my latest commits fix this.

It was actually due to clients not sending http authentication data on 
the initial AutoDiscover request. Should be fixed now.
10/02/2013 01:11:46 PM Michael Rubinsky Comment #3
Assigned to Michael Rubinsky
State ⇒ Feedback
Reply to this comment
For testing I reverted the change and now the authentication id 
usage is correct. Even with correct authentication id the 
authentication still seems to fail in some cases.
This is incorrect. The email -> user_id mapping is attempted in 
Horde_Activesync::authenticate(), which is why it was removed from 
Horde_ActiveSync_Request_Autodisocover::handle(), it was redundant.
Could it be possible that the activesync driver in horde sometimes 
sends a mangled or broken password to the authenticating activesync 
/ mail server?
You are going to need to debug this and figure out what the values for 
user and password are that are being passed around, I can't reproduce 
this.
10/02/2013 11:03:45 AM leena (dot) heino (at) uta (dot) fi Comment #2 Reply to this comment

[Show Quoted Text - 13 lines]
For testing I reverted the change and now the authentication id usage 
is correct. Even with correct authentication id the authentication 
still seems to fail in some cases.

Could it be possible that the activesync driver in horde sometimes 
sends a mangled or broken password to the authenticating activesync / 
mail server?
10/02/2013 10:45:35 AM leena (dot) heino (at) uta (dot) fi Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ inconsistent authentication id usage within the activesync
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
It seems this change might have broken authentication with Activesync 
autoconfigure in some cases: d048b5a83c04ec489b15fbbcfa2a8cd354a1d384

Previously Autosync autoconfigure in horde always seemed to use only 
the username to authenticate to the activesync / mail server server, 
but after this or perhaps some other change in the activesync code it 
now seems to use both the username and the email address for 
authentication.

Would it be possible to revert this change or modify the code so that 
activesync driver consistently uses username to authenticate to 
activesync server?

Saved Queries