Hello. Thank you for your reply. I have many applications using a db to manage access and profiles. Now I have to use even other application supporting ldap. So I’m hoping to use same db, so I can manage only a datasource for all Applications (same users!!!) But I need to use memberOf to manage the access to theese applications (profiling).
(Excuse me for My English!)
Thanks, Arianna
Il giorno gio 2 ago 2018 alle 19:54 Quanah Gibson-Mount quanah@symas.com ha scritto:
--On Thursday, August 02, 2018 5:25 PM +0200 Arianna Milazzo arianna@ariannamicrochip.it wrote:
Hello! I use OpenLDAP wuth MySQL backend.
The MySQL backend is experimental and generally unsupported. It should not be used as a general purpose backend for an LDAP server.
Can someone help me?
Is there a particular reason you're trying to wedge memberof support into mysql, which is likely not designed to handle it?
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
On 8/2/18 8:02 PM, Arianna Milazzo wrote:
I have many applications using a db to manage access and profiles. Now I have to use even other application supporting ldap. So I’m hoping to use same db, so I can manage only a datasource for all Applications (same users!!!)
You can simply keep the SQL DB and OpenLDAP DB in sync with a custom script. It's probably less work implementing it than dealing with all the issues you will have using back-sql with various overlays (e.g. slapo-memberof).
Ciao, Michael.
Hello! You're right, but already that database is populated by various scripts. I don't want to add sync scripts yet. Since I see memberOf in LDAP view, I thought the search was working too. :(
Nobody was able to use group research? I miss only this last step and then everything should be ok.
Thanks, Arianna
2018-08-07 6:26 GMT+02:00 Michael Ströder michael@stroeder.com:
On 8/2/18 8:02 PM, Arianna Milazzo wrote:
I have many applications using a db to manage access and profiles. Now I have to use even other application supporting ldap. So I’m hoping to use same db, so I can manage only a datasource for all Applications (same users!!!)
You can simply keep the SQL DB and OpenLDAP DB in sync with a custom script. It's probably less work implementing it than dealing with all the issues you will have using back-sql with various overlays (e.g. slapo-memberof).
Ciao, Michael.
--On Tuesday, August 07, 2018 11:23 AM +0200 Arianna Milazzo arianna@ariannamicrochip.it wrote:
Hello! You're right, but already that database is populated by various scripts. I don't want to add sync scripts yet. Since I see memberOf in LDAP view, I thought the search was working too.
I will reiterate again that back-sql is an *experimental* *unsupported* backend that has numerous known bugs and is *not* meant to be used as a fully compliant LDAP backend. It is a bridge, and many features that work with compliant backends do not work with it. Trying to force LDAP functionality with back-sql is going to work well as a path to pursue. In addition, all development of this backend has ceased and no one has volunteered to continue improving/developing it. It's primary purpose at the moment generally revolves around being able to return SQL data via the LDAP protocol. It is *not* to provide LDAP like functionality with SQL as the backend.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
--On Tuesday, August 07, 2018 1:30 PM -0700 Quanah Gibson-Mount quanah@symas.com wrote:
--On Tuesday, August 07, 2018 11:23 AM +0200 Arianna Milazzo arianna@ariannamicrochip.it wrote: Trying to force LDAP functionality with back-sql is going to work well as a path to pursue.
*is not going to work well.
--Qunah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org
-
Arianna Milazzo -
Michael Ströder -
Quanah Gibson-Mount