[Tickets #5844] Re: inconsistency when using _username_{from,to}backend hooks

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5844
-----------------------------------------------------------------------
 Ticket             | 5844
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | inconsistency when using _username_{from,to}backend hooks
 Queue              | Horde Framework Packages
 Version            | HEAD
 Type               | Bug
-State              | Unconfirmed
+State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2007-11-11 16:06) wrote:

So, to make sure I'm clear on what the fixes would be:

- When displaying usernames with shares, run them through
username_hook_frombackend
- When saving usernames for shares, run them through
username_hook_tobackend

That seems pretty straightforward and in the spirit of those hooks. The
other stuff, though, is getting a little hairy. The username hooks have
historically been for translating the username to _the_ backend username,
across all backends, not just to the Horde backend. Many people would use
them to translate a user-friendly username to a fully qualified username
that is then used for all services, like LDAP.

So I think a different concept or hook might be necessary to represent a
"Horde internal" vs. "All other external" username.