Hello,

No, no LDAP (or other enterprise directory) connectivity is planned.
It could be an interestion evolution.
I registered it as #324 in the track Database.
Therefore :
- it is not a high priority task,
- only authentication could be managed through LDAP, habilitation should remain in Project'Or RIA (at least in a firts time, to keep it generic)

Regards.
Babynus

hi babynus

i begin working on this task, cause i need it for start our test with your project.

i connect on SVN repository, and i found a new V1.8, i use it.

my short plan :
add parameters in /tool/config.php (finish)
add new colum in table user, for identify user source (lock : passsword change, profil data ..) (next)
do new job in user class (new method or modify existing, getSqlElementsFromCriteria)
add new test in /tool/logincheck.php, depending on parameter.

Add new button on creation user pannel for import from Ldap.
add capability to auto create user when login attemp (fail in database but succes on Ldap) with mail to admin

best regards

Hi,
Great you can improve the project !!

V1.8 branch is the correct one to strat from.
Just pay attention that I frequently commit on this branch, to be sure get latest version.

add parameters in /tool/config.php (finish)

/db/maintenance.php must also be updated to automatically add the parameter on upgrading versions (config.php is displayed only at firts run)

do new job in user class (new method or modify existing, getSqlElementsFromCriteria)

imo new method in user class seems better (getSqlElementsFromCriteria is a very generic method used for all classes). You can also redefine getSqlElementsFromCriteria in class user, but then don't forget to call parent::getSqlElementsFromCriteria when needed.

Could you summarize how you expect to manage LDAP integration ?
- interface integrating LDAP users into user table ?
- direct LDAP control : how will you manage LDAP structure : only fit one mandatory LDAP structure, or define parameters to be able to fetch correct information on any LDAP structure ?
-how will you manage the link between LDAP users and resources and contacts ? (today, users, resources and contacts are stored in a single table, one line it possible to point to user and/or resource and/or contact (throught isUser, isResource and isContact flags).
These are the points that stopped me from investigating in LDAP interface...

Many thanks.
(you may reply to support@toolware.fr if you wish).

hi

OK : i update frequently from SVN

/db/maintenance.php can add new parameters to configuration file, but how site admin can edit it, for set specific value ?
when i remove parametersLocation.php, field in config.php seems restaure to default value, it's possible to load value from parameters.php ?

I add a new column in table User : isLdap, for store 0/Null if user is local, and number for 'identifiaction source' (1 : default ldap in parameter.php)

my first need, is to use same authentification source (and creation) for user, in my case, we use ActiveDirectory, then a begin to map property on user from this schema.

i need some help for use correctly framework : i send you mail on support.

Regards

/db/maintenance.php can add new parameters to configuration file, but how site admin can edit it, for set specific value ?

JJust add new line in $versionParameters, 'V1.8.0'=>array('newParameterName'=>'defaultValue'.

when i remove parametersLocation.php, field in config.php seems restaure to default value, it's possible to load value from parameters.php ?

not done yet, but it could be an improvement.

I add a new column in table User : isLdap, for store 0/Null

Better store it as int(1) with default value to zero (so will ne ver be null), and manage it as a boolean.