LDAP default group

Author Message

Samuel Sauder

Monday 09 January 2006 11:21:20 am

I am having some struggles understanding how LDAPUserGroup configuration works. Please help me sort this out. Or if it is a developer question and I should post it in that forum, let me know.

1) Does this particular group name have to exist on the LDAP server as well? I know it needs to exist on the EZp side.

2) What is the purpose of making this configuration item an array? If I use the ldap cron job that synchronizes any changes in a persons group definitions, what is this group listing for? I can see the logic that if you specify one group it behaves as an LDAP specific guest group (if you want to keep regular guests separate).

3) Does the order of groups coming from the LDAP server have any correlation to the logic being used in ldapuser classes and cronjob? Or in the configuration of my default group?

My experience so far...
I have attempted to use the default group idea but I am running into a strange issue where things start to misbehave if my first group listed from LDAP is not yet setup in EZp.

EZpublish 3.7.2

Samuel Sauder

Wednesday 11 January 2006 10:38:00 am

I finally got it to work. I will attempt to answer my own questions.

1. no

2. still don't know why this could be an array...

3. no and no.

What I did find that worked is that my default LDAP group needs to be inside another User Group. If it is at the root of the Users object, things may fail.

j jevack

Thursday 02 February 2006 4:04:01 am

Samuel,

Regarding the LDAPUserGroup configuration, did you find the following to be an accurate explanation of how things worked (this is a part of another ldap forum post):
<i>
If the LDAPUserGroup is an array, then the first one will be the default placement of ldap users. If it's not, then all ldap users are stored in the same eZ publish user group.

LDAPUserGroupAttributeType and LDAPUserGroupAttribute are used to specify which attribute of the ldap user object eZ publish should use when deciding where to place the users.

So, an example:
LDAPUserGroupType=name
LDAPUserGroup[]=Default
LDAPUserGroup[]=Secretary
LDAPUserGroup[]=Clerk
LDAPUserGroup[]=Boss
LDAPUserGroupAttributeType=name
LDAPUserGroupAttribute=employeetype

Now, when logging in, eZ publish looks at the LDAP object, and finds the attribute whose name is employeetype, and reads its value. Then, eZ publish searches for an eZ publish user group whose name equals the given value. If it is found, then the user is stored there. If not, it is stored in Default.
</i>

I'm having trouble getting users stored in appropriate ezp groups. At this point, ezp is putting a user in every group specified in the LDAPUserGroup array regardless of the values in the LDAPUserGroupAttributeType/LDAPUserGroupAttribute variables.

Thanks

Jason

Daniel Sippel

Monday 27 February 2006 2:09:33 am

Hello j jevack!

I experienced the same problem as you with eZ publish 3.7.3, but I think this is not a bug.

You have to specify only ONE LDAPUserGroup[], the one where the default LDAP-Users should be placed.
Every time a user logs in and his LDAP attribute e.g. employeeType matches an existing group name in eZ publish, he will be placed in this group.

Daniel

Samuel Sauder

Tuesday 28 February 2006 7:09:48 am

Jason, from my experience Daniel is correct. Default means "if I can't find any (existing in EzPublish) groups that match (to LDAP groups) for this user." So if you define LDAPUserGroup as an array, it means if there is no match assign them to all these groups.

(I think the above quote and example you mentioned is misleading.)

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 30 2025 22:23:58
Script start
Timing: Jan 30 2025 22:23:58
Module start 'layout'
Timing: Jan 30 2025 22:23:58
Module start 'content'
Timing: Jan 30 2025 22:23:59
Module end 'content'
Timing: Jan 30 2025 22:23:59
Script end

Main resources:

Total runtime1.1012 sec
Peak memory usage8,192.0000 KB
Database Queries65

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0052 588.1328151.2109
Module start 'layout' 0.00530.0047 739.3438220.6875
Module start 'content' 0.01001.0904 960.03134,271.7500
Module end 'content' 1.10030.0009 5,231.781311.8594
Script end 1.1012  5,243.6406 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00350.3133160.0002
Check MTime0.00120.1053160.0001
Mysql Total
Database connection0.00070.062610.0007
Mysqli_queries1.018092.4377650.0157
Looping result0.00060.0542630.0000
Template Total1.048795.220.5243
Template load0.00170.158320.0009
Template processing1.046995.065220.5235
Template load and register function0.00170.152310.0017
states
state_id_array0.00170.156710.0017
state_identifier_array0.00200.185120.0010
Override
Cache load0.00150.1371440.0000
Sytem overhead
Fetch class attribute can translate value0.00190.172530.0006
Fetch class attribute name0.00190.174650.0004
XML
Image XML parsing0.00050.044530.0002
class_abstraction
Instantiating content class attribute0.00000.001150.0000
General
dbfile0.00070.0620100.0001
String conversion0.00000.000740.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
5content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
10content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
5content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 22
 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs