[Tickets #12186] Re: activesync component does not username canonified by authusername() hook
noreply at bugs.horde.org
noreply at bugs.horde.org
Mon Apr 22 16:04:01 UTC 2013
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/12186
------------------------------------------------------------------------------
Ticket | 12186
Updated By | Michael Rubinsky <mrubinsk at horde.org>
Summary | activesync component does not username canonified by
| authusername() hook
Queue | Horde Base
Version | Git master
Type | Bug
State | Resolved
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Rubinsky
------------------------------------------------------------------------------
Michael Rubinsky <mrubinsk at horde.org> (2013-04-22 16:04) wrote:
> Thanks for the quick response. But the patch seems to make things
> worse. Some more words about my setup:
<snip>
> Without the patch:
>
> * entering 'a' as its userid on a Android devices associated the
> device; but it is visible to the administrator in the global
> activesync device list. User 'a' does not see it in its
> configuration screen.
The patch will not fix devices that have already paired with the
server. You will need to either have the users create a new account on
the device, or an admin can remove the device state on the server. In
other words, only newly created devices will be saved with the
correctly normalized username.
> * entering 'a at realm.org' as userid made the device visible to the
> user too. But I had to wrote a preauthenticate() hook which strips
> the '@realm.org' away. Without this hook, authentication to mailbox0
> happens as 'a at realm.org'.
>
> With the patch the device is not visible anymore for the last point.
This is expected. A user should only be able to login on the device
with the same username he logs in to horde with on the desktop.
More information about the bugs
mailing list