Title: Message Title
|
|
|
|
As Mark mentions, I believe your use case can already be achieved by simply giving the "Special Group" proper permissions.
As a basic example:
1. Map a particular Shibboleth attribute to a DSpace "Special Group" (using "role" settings in authentication-shibboleth.cfg)
2. Give that "Special Group" Administrative (or other) permissions on the Community or Collection (by adding that "Special Group" as a subgroup of the Community or Collection ADMIN group, or whatever other group gives them the proper permissions).
After doing so, anyone who logs in and is added to the "Special Group" will automatically gain administrative privileges on that Community/Collection for the remainder of their session. Those privileges will never be stored in the DSpace database. But, the next time they login, they will again receive those privileges (as they'll again be added to that Special Group for the remainder of their session).
Is there something we are missing? Would this work for your use case?
|
|
|
|
|
|
|
|
The Shibboleth-Authentication module may add authenticated users to DSpace groups. These groups are called special groups, "these are really groups but the user's membership within these groups is not recorded in the database. Each time a user authenticates they are automatically placed within the pre-defined DSpace group, so if the user loses their affil...
|
|
|
|
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
