| Summary | use user's id of a user's default share |
| Queue | Turba |
| Queue Version | 2.2.1 |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | develop (at) kristov (dot) de |
| Created | 07/06/2008 (6211 days ago) |
| Due | |
| Updated | 07/30/2008 (6187 days ago) |
| Assigned | |
| Resolved | 07/06/2008 (6211 days ago) |
| Milestone | |
| Patch | Yes |
configuration of any number of both shared and unshared sources, so
just using the user name to create a new 'default' share would not
work since it's possible to have more than one shared source.
in the Horde database when ldap server is modified (name of the
adressbook, ldap entry deleted, ...). Those scripts are based on the
uid. I tried the patch and it works fine. The first adressbook created
has datatree_name=uid and the others have a number. What kind of
problem do you think about ?
State ⇒ Rejected
configuration of any number of both shared and unshared sources, so
just using the user name to create a new 'default' share would not
work since it's possible to have more than one shared source.
Priority ⇒ 1. Low
New Attachment: horde-turba-2.2.1-sharename.patch
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Turba
Summary ⇒ use userÄsid of a user's default share
Type ⇒ Enhancement
State ⇒ New
turba chooses a random identifier when creating a missing user's
default share. The other mentioned applications choose the user
authentication id as it is reasonably unique for that purpose. I
propose to adapt turba to that practice if no arguments exist against
it.