Feature #2031: when using LDAP, an empty record is written in the user table - Repository - Chamilo Tracking System

Feature #2031

when using LDAP, an empty record is written in the user table

Added by Olivier Sourie about 9 years ago. Updated over 7 years ago.

Status:

Bug resolved

Priority:

Low

Assignee:

Target version:

Chamilo LCMS Connect - LCMS 3

Start date:

19/09/2010

Due date:

% Done:

Estimated time:

Complexity:

Normal

Description

At Howest we use connection to an LDAP-server to authenticate our users.
Accessing user information with the LDAP-parameters in Chamilo 2.0 works fine.
However, it goes wrong when the default properties of the User Object in the 'create' method of the database Class are used: there is nog data of the user in these properties.

History

Updated by Sven Vanpoucke about 9 years ago

Category set to 21
Status changed from New to Needs testing
Assignee set to Sven Vanpoucke
% Done changed from 0 to 100

Fixed the ldap problems
http://code.google.com/p/chamilo/source/detail?r=3f04b4cc2cd5d64877b4b94ac1cacf841c89fb1e&repo=chamilo

Updated by Hans De Bisschop about 9 years ago

Status changed from Needs testing to Assigned
% Done changed from 100 to 50

This is only a partial fix, something should be donne about the hardcoded ldap property names too.

Updated by Sven Vanpoucke about 9 years ago

The hardcoded properties are seperated in a parser class, when using the ldap connection, one needs to adapt the parser class to connect.

Updated by Sven Vanpoucke about 9 years ago

Status changed from Assigned to New
Assignee deleted (~~Sven Vanpoucke~~)

Due to many differences in ldap structure, a simple mapping system saved in settings / xml files is not enough to parse an ldap record to a chamilo users. In some cases very specific parse methods are needed like loops etc.