The Shibboleth V2 IdP and SP software have reached End of Life and are no longer supported. This documentation is available for historical purposes only. See the IDP v4 and SP v3 wiki spaces for current documentation on the supported versions.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Current Thinking

  1. Meaning of consent --  user provides a YES/NO to a complete specific set of attributes (however that list is developed). This may include a check box for "Don't ask me again for this site".
  2. Deferred -- user provides a YES/NO to each attribute that potentially can be released. Does not allow user to create a new policy. We think that, currently, most SPs requirements are quite simple.

Notes, Issues and Constraints

  1. Within the UK, the epTID attribute value is NOT considered to be "personal information". Some felt that is was an aggressive position, advantageous to the campuses.
  2. Within the US, we expect different institutions will adopt a variety of policies on this issue. It might be useful to test this idea with the Dept of Edu.
  3. EPPN's re-assignability makes it somewhat problematic as a permanent identifier. However, its value seems to be a function of the application. epTID works fine with RefWorks; EPPN works better with a wiki (even with re-assignability). What do we preach to developers? EPPN is "collaboration friendly" --friendly to the user, friendly to others.
  4. At some institutions, people don't know how to obtain their value for this attribute.

Related Projects

some text

  • No labels