Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Recap of consensus so far - note that all changes will need to be validated via the consultation process
    1. The FAQ will be revised to offer clarity on the term "affiliation" (see Research and Scholarship FAQ) and editorial changes made to the spec to make it more clear (see new draft spec for updated structure)
    2. eduPersonScopedAffiliation will become a required value
    3. R&S will require privacy statements
    4. subject-id should be listed as the new identifier
    5. R&S 1.3 and R&S 2.0 can co-exist; no migration detail will be included in the spec itself.
    6. ePPN and targeted ID to both be removed from R&S 2.0
    7. Information on OIDC requirements will be moved to R&S 2.1 (after the OIDF OIDCre working group has formal documentation in this space)
    8. eduPersonAssurance will be required, RAF recommended
  2. Home Organization use case, continued

    1. introducing schacHomeOrg to R&S (which will be a lift since SCHAC isn't globally used), or adding a value to eduPersonScopedAffliation (which has its own lift) - POLL
    2. need clarity on the complex use cases (or real-world examples) to help describe what the IdP would assert when the IdP has several different organizations involved
      1. Miro and Christos did not have time to write this up. The use case we had talked about was the mobility use case.
      2. One case to argue for is a proxied scenario where an IdP is fronting several organizations (e.g., a proxy or a hub-and-spoke federation). If you don't assume they are asserting attributes that would mask the proxy, you could do that by making the proxy a detail where it would not be asserting affiliations in the proxy's namespace. Instead, they would add information from whatever organizations they are proxying. This isn't spelled out anywhere as a rule or even best practice guidance. In this proxy use case, in order to do that would need an attribute to carry this information. We could write language in the spec that this isn't expected to be supported within R&S.
      3. It may be that this is really too specific for R&S. How globally would this be used? Can we add this requirement when it will not be used out of this specific, European use case?
      4. The AARC community is very interested in ways to use ScopedAffiliation. There is a gap in the available required values; a gap that might impact this use case is that if someone doesn't qualify as a member, then there is no way to indicate another relationship to the organization. Should an IdP allow an authentication to proceed if it can't assert any eduPersonScopedAffiliation value? It is valid because R&S doesn't have to be universal, but we also need more text about this. We will need to say something somewhere about what to do if there is no affiliation with the institution when asserting something in eduPersonScopedAffiliation.
      5. As a service provide, I need to have a way to verify that the user has a relationship with the institution. Does a visiting individual (guest) count as any kind of member to the organization?
      6. If a hub-and-spoke org asserts "student@hub" and not "student@university" that would be a problem for this use case. If we can say that the scope of eduPersonScopedAffiliation is the home organization, then we can use this.
      7. Interesting reading
        1. AARC G025 on expressing affiliation

        2. AARC Guidelines on expressing group
          membership and role information may be useful as well.
      8. Poll: How should we handle the need for home organization in R&S 2.0? Require schacHomeOrg - 0%; Add guidance for the use for eduPersonScopedAffiliation - 90%; Do nothing (don't try to support this use case in R&S) 10%; Need more information - 0%
      9. We will need more information on what guidance we want to offer here; the guidance in the spec should describe what to do in the use case when using this attribute. Scott will propose text in the draft.
  3. Proposal to require DisplayName (Petersen Peter S) - POLL
    1. There is a functional reason why DisplayName and the other names are different. The DisplayName was the more generally useful case.
    2. What to do if there is only one name? What should an institution use if they have no value for a part of the name? We need to offer guidance if we start requiring this.
    3. We'll need to remind people that "required" means it's present when it can be, but if there is no value (e.g., no givenname) then that's valid. There is concern that SPs will be making decisions to split on whitespace whatever is provided in DisplayName, which may be bad.
    4. Poll: Should R&S 2.0 require DisplayName AND require given/sn? Yes, DisplayName and Given/SN should all be required - 60%; No, they should be left as is (optional) - 0%, It should only require DisplayName, with Given/sn as optional - 30%; I need more information - 10%
    5. We'll update the draft to require DisplayName and givenname/sn, and we'll see what comes out of the consultation. Note that we're not trying to drive SPs to any particular behavior here; we're trying to given them what's most commonly useful, respecting cultural impertatives.