Hi everyone
I'm beginning to suspect the LDAP Special Groups code in DSpace 3.0 is
broken
Please see the scenarios below, which are excerpts from
/home/dspace/config/modules/authentication-ldap.cfg
Scenario 1
login.groupmap.1 = OU=StaffUsers:all-staff
login.groupmap.2 = OU=StudentUsers:all-students
In practice newly authenticated new staff are added to the all-staff,
all-authenticated and anonymous groups. Newly authenticated students only
belong to the anonymous group
Scenario 2
##### Added By Clive Gould on 31/07/13 to allow for special groups
# login.groupmap.1 = OU=StaffUsers:all-staff
# login.groupmap.2 = OU=StudentUsers:all-students
login.groupmap.1 = OU=StudentUsers:all-students
In practice newly authenticated students are added to the all-students,
all-authenticated and anonymous groups. Newly authenticated staff only
belong to the anonymous group
Scenario 3
# login.groupmap.1 = OU=StaffUsers:all-staff
# login.groupmap.2 = OU=StudentUsers:all-students
login.groupmap.1 = OU=StudentUsers:all-students
login.groupmap.2 = OU=StaffUsers:all-staff
Newly authenticated students are added to the all-students,
all-authenticated and anonymous groups. Newly authenticated staff only
belong to the anonymous group
Conclusion
It looks horribly as if only the first line login.groupmap.1 is being
processed. login.groupmap.2 seems to be ignored
Note: If a member of staff or student has logged in and registered once
their membership of the special groups appears to be persistent through
multiple logins
I'm not a Java programmer and haven't time try to understand and debug the
code myself. Has anyone actually got this special groups code to work
properly or is this a bug that needs fixing?
Any ideas anyone?
Clive
On Tue, Aug 6, 2013 at 10:11 AM, helix84 <[email protected]> wrote:
> Neither login.specialgroup nor login.groupmap are applied to student,
> but it is to staff? I'm as baffled as you are.
>
> Are you modifying the right config file, i.e.
> [dspace]/config/modules/authentication-ldap.cfg (maybe you
> accidentally edited the one in [dspace-source])?
>
> Other than that, try sprinkling more log.debug calls around to see
> which branches of code are executed. Basically you want to check the
> values that drive the decisions in any relevant "if" statements.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
