[Tickets #12186] Re: activesync component does not username canonified by authusername() hook

[noreply at bugs.horde.org]

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

Ticket-URL: http://bugs.horde.org/ticket/12186
------------------------------------------------------------------------------
  Ticket           | 12186
  Aktualisiert Von | enrico.scholz at sigma-chemnitz.de
  Zusammenfassung  | activesync component does not username canonified by
                   | authusername() hook
  Warteschlange    | Horde Base
  Version          | Git master
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       | Michael Rubinsky
------------------------------------------------------------------------------


enrico.scholz at sigma-chemnitz.de (2013-04-23 17:07) hat geschrieben:

> 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.

I tried it but the user 'a at realm.org' still does not see it and device  
is listed for user 'a' in the administrator overview.

A

| select * from horde_prefs;

lists 'a at realm.org' as pref_uid.  But

| select * from horde_activesync_device_users;

returns an entry with the non-canonified 'a' user only.


> 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.

That's the case here.  User is loggin in as 'a' in the webfrontend and  
enters 'a' as userid in the android email application.

The webfrontend calls "authusername('a', True) -> 'a at realm.org'" while  
ActiveSync seems to miss this step.