can I create two ldap LoginHandler ?

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
akiuni sanka	Thursday 20 May 2010 12:05:19 am Hello I need to authentify my users from 2 different Active Directory domains (=> 2 LDAP servers with different configuration inside). Does somebody has already done this ? If not, how can I do that ? I haven't found any post... I was wondering if I could copy the ldap.ini to ldap2.ini, and then create a ldap2.ini.append.php where I configure the second domain configuration. Lastly, I could add a loginHandler in the site.ini.append.php. This would become : [UserSettings] LoginHandler[] LoginHandler[]=LDAP LoginHandler[]=LDAP2 Can you tell me if this could work ? if not, have you an idea on how to build my 2 domains authentication ? thanks in advance.... akiuni
Bertrand Dunogier	Thursday 20 May 2010 1:23:59 am Well, technically, you can chain multiple login handlers. This is what is usually done with LDAP, actually: first standard, so that the local user can be tried first, then LDAP as a fallback. So if you have 2 different LDAP login handlers, the second one will be used if the first one fails, as simple as that. Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
akiuni sanka	Thursday 20 May 2010 4:14:21 am thanks for your answer Bertrand, do you think that the "ldap2" trick will work ? I just fear that ezpublish won't accept it...
akiuni sanka	Thursday 20 May 2010 4:32:28 am ok, I had a look to the sources files and I think that I have found my answer. The "ldap.ini" file is hardcoded in the following file : ./kernel/classes/datatypes/ezuser/ezldapuser.php : $LDAPIni = eZINI::instance( 'ldap.ini' ); so I guess that ezpublish won't accept my ldap2 without creating a new type of users... ezldap2user for exemple. thanks akiuni

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 31 2025 01:25:56
Script start
Timing:	Jan 31 2025 01:25:56
Module start 'layout'
Timing:	Jan 31 2025 01:25:56
Module start 'content'
Timing:	Jan 31 2025 01:25:56
Module end 'content'
Timing:	Jan 31 2025 01:25:56
Script end

Main resources:

Total runtime	0.0206 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0043	588.2578	151.2266
Module start 'layout'	0.0043	0.0036	739.4844	220.7188
Module start 'content'	0.0079	0.0114	960.2031	997.8359
Module end 'content'	0.0193	0.0013	1,958.0391	33.9922
Script end	0.0206		1,992.0313

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	11.6588	14	0.0002
Check MTime	0.0010	4.8380	14	0.0001
Mysql Total
Database connection	0.0005	2.4213	1	0.0005
Mysqli_queries	0.0021	10.3446	3	0.0007
Looping result	0.0000	0.0532	1	0.0000
Template Total	0.0009	4.2	1	0.0009
Template load	0.0007	3.3422	1	0.0007
Template processing	0.0002	0.8781	1	0.0002
Override
Cache load	0.0005	2.3045	1	0.0005
General
dbfile	0.0003	1.2483	8	0.0000
String conversion	0.0000	0.0335	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs