Hi all, I work with Shaun. I was wondering if it has something to do with the fact that LDAP users only get added to the "Staff" group (which we set up) for their session, not on a permanent basis.
So, if I log in as an LDAP user and (leaving them logged in) then go to another machine and log in as an administrator and open up the group edit interface (/tools/group-edit), I do not see my LDAP username listed in the "Staff" group. Is this normal? Is something perhaps going wrong there? The setting in the config file is : login.specialgroup = staff We appreciate any help or advice the community can give us on debugging this problem. On Thursday, 9 March 2017 11:55:56 UTC+2, Shaun Whitaker wrote: > > Hi, > > A group has been set up in our system and has been giving Admin > permissions to certain Communities. When we log in with an LDAP user and we > try start a new submission from the "My DSpace" page, the following message > pops up: > > When manually browsing to the community this user has full access to all > collections and can then submit to any of the collections within that > community. I've tried setting admin permissions to all communities but this > did not work either. > > Is there any particular reason why it's doing this? Perhaps we missing a > setting somewhere? > > using Dspace 5.2 > > Thanks for the assistance, > Shaun. > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
