InCommon Technical Discussions

["Basney, Jim" <>]

On 6/8/17, 6:36 AM, Scott Koranda wrote:
> We will plan to notify the IdP operator of the issue, but often the IdPs
> that present this issue also have incorrect contact information in
> metadata and/or do not respond on a timescale useful to the VO, so it is
> better from the VO perspective to just use the normal vetting process to
> process the "new" enrollment and get the user back to accessing the SPs.

Indeed. When CILogon attempted on Monday to notify an InCommon IdP operator 
about their ePTIDs changing, the mail bounced ("User unknown"). We're looking 
forward to the checks for contacts in metadata that are part of the planned 
Baseline Expectations Implementation [1]. I'm also looking forward to using 
the ORCID iD linking added in the recent COmanage release to help us avoid 
re-vetting users, since ORCID gives us long-lived persistent IDs. Until then, 
we have no choice but to re-enroll the users (which we're doing for another 
InCommon IdP this week).

-Jim

[1] https://spaces.internet2.edu/x/05iTBg