Sorry for the late reply. After investigating what I found was I had not given the a policy to each group for the "submitter"
All is working! Moving forward rapidly!
Texas Woman's University
Director of Library Information Technology & Technical Support
PO Box 425528
Denton TX 76204-5528
From: ivan.masar@... [mailto:ivan.masar@...] On Behalf Of helix84
Sent: Wednesday, August 28, 2013 2:57 AM
To: Schuster, David
Subject: Re: [Dspace-tech] LDAP config - DS-1576?
On Wed, Aug 28, 2013 at 12:08 AM, Schuster, David <dschuster@...> wrote:
> I am running dspace 3.2 and have LDAP running, but when I assigned a group of "submitter" in LDAP and have a group for that with all of the collections in it as people log in they are not assigned to anything.
* Is this using login.specialgroup (this should work) or using login.groupmap.*? As I wrote before, it seems only login.groupmap.1 works, the rest is broken.
* Just to make sure, are you aware that LDAP group membership is transient, not recorded anywhere in DSpace and has to be checked via user profile?
* Where is your group membership stored in LDAP? login.groupmap.* takes it from DN (e.g. uid=dschuster,dn=STAFF,dn=twu,dn=edu). It can be also stored in attribute - DSpace currently doesn't support that, but I'd like to implement it for DSpace 4.0 because we just switched to this locally.
> I also tried a particular collection and it didn't assign the new person into it either. Does that make sense? I would love to "test" anything you can throw at me!
There is a catch there with collection rights, are you aware of this?