Hello all,
This post may be a little OT, but i'm sure this subject has bitten some of you some time. So, i'm willing to take the chance. Anyway, feel free to redirect me and this conversation elsewhere.
Background:
There's an LDAP infrastructure set up, which has been fed and maintained by a "in the house" made management system.
This management system primary role is NOT to manage LDAP data, but it was where the data lived, some extensions where developed to provide that extra functionality. Years have passed and more and more we depend on our LDAP service. But we also have more and more the need to add other data to LDAP, which doesn't exist in the still in place management system. Changing the LDAP data model has also become a major headache since that type of change will also force maintenance to the management system accordingly.
Objective:
I'm currently delegated to find a modular solution that can aggregate data from several sources, relational databases, other ldap servers, flat text files, whatever, and be able to maintain a centrally managed information database which can then be exported to/served by an LDAP server. The solution could aggregate data directly into an LDAP database, or it could maintain it's own database that could be later exported to ldif, or sync to LDAP.
The main purpose here would also to be able to find something that would do this, or that could be set with some minimal changes to perform as described, WITHOUT being an "in the house" solution.
Sorry if it felt like i'm daydreaming, but i would love to hear peoples thoughts on this matter.
Best regards,
Hugo Monteiro.
Am Fri, 15 Apr 2011 12:12:49 +0100 schrieb Hugo Monteiro hugo.monteiro@fct.unl.pt:
Hello all,
This post may be a little OT, but i'm sure this subject has bitten some of you some time. So, i'm willing to take the chance. Anyway, feel free to redirect me and this conversation elsewhere.
Background:
There's an LDAP infrastructure set up, which has been fed and maintained by a "in the house" made management system.
This management system primary role is NOT to manage LDAP data, but it was where the data lived, some extensions where developed to provide that extra functionality. Years have passed and more and more we depend on our LDAP service. But we also have more and more the need to add other data to LDAP, which doesn't exist in the still in place management system. Changing the LDAP data model has also become a major headache since that type of change will also force maintenance to the management system accordingly.
Objective:
I'm currently delegated to find a modular solution that can aggregate data from several sources, relational databases, other ldap servers, flat text files, whatever, and be able to maintain a centrally managed information database which can then be exported to/served by an LDAP server. The solution could aggregate data directly into an LDAP database, or it could maintain it's own database that could be later exported to ldif, or sync to LDAP.
The main purpose here would also to be able to find something that would do this, or that could be set with some minimal changes to perform as described, WITHOUT being an "in the house" solution.
Sorry if it felt like i'm daydreaming, but i would love to hear peoples thoughts on this matter.
What you are looking for is some sort of Meta Directory. There are some open source products available as well as commercial products. On the other hand, OpenLDAP provides some backends like back-perl and back-sock in order to provide such service.
-Dieter
You could also use the SQL backend for slapd AFAIK. Please see the man page of slapd-sql for more information.
Matheus Morais
On Tue, Apr 19, 2011 at 7:40 AM, Dieter Kluenter dieter@dkluenter.dewrote:
Am Fri, 15 Apr 2011 12:12:49 +0100 schrieb Hugo Monteiro hugo.monteiro@fct.unl.pt:
Hello all,
This post may be a little OT, but i'm sure this subject has bitten some of you some time. So, i'm willing to take the chance. Anyway, feel free to redirect me and this conversation elsewhere.
Background:
There's an LDAP infrastructure set up, which has been fed and maintained by a "in the house" made management system.
This management system primary role is NOT to manage LDAP data, but it was where the data lived, some extensions where developed to provide that extra functionality. Years have passed and more and more we depend on our LDAP service. But we also have more and more the need to add other data to LDAP, which doesn't exist in the still in place management system. Changing the LDAP data model has also become a major headache since that type of change will also force maintenance to the management system accordingly.
Objective:
I'm currently delegated to find a modular solution that can aggregate data from several sources, relational databases, other ldap servers, flat text files, whatever, and be able to maintain a centrally managed information database which can then be exported to/served by an LDAP server. The solution could aggregate data directly into an LDAP database, or it could maintain it's own database that could be later exported to ldif, or sync to LDAP.
The main purpose here would also to be able to find something that would do this, or that could be set with some minimal changes to perform as described, WITHOUT being an "in the house" solution.
Sorry if it felt like i'm daydreaming, but i would love to hear peoples thoughts on this matter.
What you are looking for is some sort of Meta Directory. There are some open source products available as well as commercial products. On the other hand, OpenLDAP provides some backends like back-perl and back-sock in order to provide such service.
-Dieter
-- Dieter Klünter | Systemberatung http://dkluenter.de GPG Key ID:DA147B05 53°37'09,95"N 10°08'02,42"E
openldap-technical@openldap.org
-
Dieter Kluenter -
Hugo Monteiro -
xsun