On Tuesday, March 28, 2017 at 5:57:05 AM UTC-4, Layale Bassil wrote: > > I have seen this question on the forums and the answer to it was to use > LDAP authentication which we are already using and then edit the > authentication-ldap.cfg file and set the logins.specialgroup = A property > and give it the name of the group created (assume = A). > > > > I did this and restarted tomcat but when I login I am not being added to > group A. If a user belongs to another group wont this apply to him when he > logs in? >
How did you determine that this is not working? You cannot make that determination by inspecting the list of members of group A. Special groups are granted to user *sessions*, not user *accounts*. Special-group membership is not permanent and is not recorded anywhere in the database. You can only discover it through the product's behavior or reading the authentication mechanism's configuration. If you request access to an object, and access is granted, and access could only be granted to a member of group A, and you are not listed among the members of group A or any group that is a member of group A (directly or indirectly), then DSpace is configured to grant you special membership in group A. -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
