[phpldapadmin] Using phpldapadmin as a end-user account management tool

Hello list.

We are trying to use phpldapadmin as a temporary solution for our end 
users to manage their own account information. The goal is to provide  a 
user-friendly interface to someone with no knowledge of what is an LDAP 
server at all, while another dedicated solution (not ldap-based) is 
being developped.

By using configuration options, and a dedicated template, I managed to 
make the interface somewhat easier, but it's still heavily 
admin-oriented. Notably, I'd like to achieve the following issues.

1) Once connected, the user has first to select its own entry on the 
tree browser on the left side. I'd like him to be directly presented its 
own entry, while still allowing to search for other entries.

2) Optional (per schema) attributes without values are not displayed at 
all. And if the 'add_attribute' command is allowed, the full list of 
non-aliased attributes is displayed, which is unpractical. As one of our 
goal is to encourage users to maintain their own telephone number, we'd 
like to either have a ready-to-use empty attribute text area, or to have 
a restricted list of potential attributes.

I also tried a default value in the template, but it override current 
value if already present (I guess this is intended for creation 
templates, not modification ones).

I also tried to call a custom function, declared in config.php that 
would either return current or default value, without succes:
<value>=php.Function(getDefaultTelephoneNumber;%telephoneNumber%)</value>
Result:
An attempt was made to call a function that doesnt exist 
(getDefaultTelephoneNumber)

3) For each available attribute, many displayed items are useless for 
end-user: 'alias', 'rdn', 'ro', 'required' mentions. Sure, it doesn't 
really hurt, but it also make 'hint' not proeminent enough, whereas we 
use it to explain important information about what is the usage of an 
attribute.

4) Some of our attributes have server-enforced constraints, such as 
telephoneNumber, which has a mandatory format. Rather than having users 
facing mysterious 'constraint violation error message', I'd like to be 
able to display those constraints on the form. I tried to use 'helper' 
for this, without success, as it is not meant to provide informations on 
how to get a value, but to get this value directly.

I guess I could use either 'hint' or 'display' values for this, but I'd 
prefer to keep their semantics distinct.

5) I'd like to be able to not allow adding additional values for some 
multivalued attributes, such as sn or givenName, even if the schema 
allows it.

I guess 3, 4 and 5 could easily get achieved by patching 
TemplateRender.php, but maybe they are better ways to achieve it now. 
And I'm more sceptic about 1 and 2.

BTW, I'm using PLA 1.2.0.4 (and I'm mandriva package maintainer, if that 
matters :P).

-- 
BOFH excuse #283:

Lawn mower blade in your fan need sharpening

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
______________________________________
phpLDAPadmin development mailing list.
To unsbuscribe: https://lists.sourceforge.net/lists/listinfo/phpldapadmin-devel
http://phpldapadmin.sourceforge.net/