Upgrade to v3 comments out unscoped-affiliation in an unmodified attribute-map.xml

Description

Shibboleth SP still has a default behavior change since v2. If a deployer used predefined attributes, e.g. eppn and unscoped-affiliation, it suddenly misses unscoped-affiliation when upgraded to v3. It should be noted in ReleaseNotes.

Predefined attributes with versions:
2.6.1: eppn, affiliation, unscoped-affiliation, entitlement, targeted-id, persistent-id
3.0.3: subject-id, pairwise-id, eppn, affiliation, entitlement, persistent-id

Environment

None

Activity

Scott Cantor March 4, 2019 at 4:10 PM

Added a mention of unscoped affiliation to the Release Notes.

Scott Cantor March 4, 2019 at 2:14 PM

Unscoped affiliation is unsafe in a federated system, so I'm comfortable with a change like that.

Fixed

Details

Assignee

Reporter

Components

Affects versions

Created March 3, 2019 at 2:56 PM
Updated March 4, 2019 at 4:10 PM
Resolved March 4, 2019 at 4:10 PM