Title: Message Title
|
|
|
|
Do you really want to grant access for a workflow step to *anyone who authenticates via Shibboleth*? Please explain your use case more fully.
The meaning of these special groups is "the current session was authenticated by the X mechanism" (where X is Shib, X.509, etc.) If I logged on yesterday using Shibboleth, and today using LDAP, then today I *should* be in the LDAP special group and *should not* be in the Shibboleth special group. Recording membership permanently would change the meaning to "the current user was authenticated by the X mechanism at some time in the past" which tells us nothing about how the user authenticated *this session*. The whole point, as I understand it, was to be able to know how *this session* was authenticated.
|
|
|
|
|
|
|
|
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
