[Tickets #6883] Re: group permission with LDAP does not work

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6883
------------------------------------------------------------------------------
  Ticket             | 6883
  Updated By         | Chuck Hagenbuch <chuck at horde.org>
  Summary            | group permission with LDAP does not work
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          | 3.2.2
  Patch              |
  Owners             | Horde Developers
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2008-08-22 21:15) wrote:

> So, do you want to add a mapping table for user shares too? Because
> we use a text field there too, and this table is much more used than
> the group shares table. And isn't an additional join eating up all
> the performance gain we get from using integer indexes?

I would prefer to have integer userids for Horde whether native or  
not, yes, to make it simpler to write apps that integrate with global  
Horde user information, and to have things like OpenID and OAuth  
server/provider support. As for adding extra joins, things like the  
current user's id would be cached in the session, and we can  
relatively easily cache other flat lists of id => username when  
needed. And joins on simple mapping tables are pretty quick even with  
millions of rows.

I can be convinced not to do this for now I guess, but I think we  
really need a global horde userid, that is an integer, for simplicity  
in Horde 4.