By end of SW Workcycle 2024 - 2, have a plan for Honeybadger notifications for discrepancy between suAffiliation and unscoped-affiliation/eduPersonAffiliation

[hudajkhan]

To date (2/22/2024), we have 252 affected users for articles#index for Honeybadger notifications stating that suAffiliation was providing access when eduPersonAffiliation (mapped to unscoped-affiliation) was not. By the end of the workcycle, we should decide if we need to remove the Honeybadger notification after the code with eduPersonEntitlement has been in production for a while and we can see if notifications persist or decrease (indicating that the addition of eduPersonEntitlement is capturing most of what we need).

[saseestone]

We're still seeing the discrepancy, so leaving this open for now.

[taylor-steve]

Huda says the first place to start here is collecting all the recent Honeybadger errors and looking for patterns & collecting unique user IDs (and if the failures are consistent for those users). If they should have access and entitlements is nil, we likely need to bring that data to Ops and work with them to determine why those properties aren't coming through (e.g., is it some shib issue).

Also she mentioned how to look at your own Shibboleth session info:

Go to https://searchworks-stage.stanford.edu/ Click Login Go to https://searchworks-stage.stanford.edu/Shibboleth.sso/Session

It's only available for a specific time window, so you may need to log out and back in for the session info to be available.

[taylor-steve]

Summary of the HB data from 10/17/2024 to present:

• 63 users with affiliations stanford:affiliate:sponsored and person_affiliation (eduPersonAffiliation) affiliate. They have no entitlements and they fail the person_affiliated? check because affiliate is not in Settings.UNSCOPED_AFFILIATION.

The following users with the listed affiliations have no person_affiliations (eduPersonAffiliation) and no entitlements (eduPersonEntitlement)

• 1 with stanford:staff:academic
• 1 with stanford:student:recent;stanford:student
• 2 with stanford:student
• 2 with stanford:student;stanford:staff:nonactive
• 4 with stanford:staff:student;stanford:student:recent
• 15 with stanford:student:incoming

[taylor-steve]

Backlogging this after the shared config changes. We should re-run the report during WC2 and see if we reduced the number of notifications.

[taylor-steve]

I ran the report again after the changes to shared config (after 04/29/2025):

• 1 with stanford:staff:student;stanford:student:recent;stanford:student:nonactive;stanford:staff:nonactive
• 1 with stanford:student
• 1 with stanford:student:incoming;stanford:staff:nonactive
• 3 with stanford:affiliate:sponsored
• 3 with stanford:staff:student;stanford:student:recent;stanford:staff:nonactive
• 7 with stanford:staff:student;stanford:student:recent

I'd hazard a guess that these are all upstream issues we can't do anything about.