Education & research | Modelled case study
Rotate federation signing keys across campus and research services
Which relying services will reject a new federation signer, and how quickly can stale metadata be corrected?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Identity Management · Library IT · Research Computing functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A university or research consortium combines student systems, federated identity, shared instruments, data repositories, partner institutions, and long-lived research records.
What is at stake
Open collaboration must coexist with durable privacy, research provenance, grant obligations, and identities that span institutions with different change windows.
Situation
Departments and external research services cache metadata differently, turning a key rollover into widespread login failure.
Event that forces action
Identity-provider migration, scheduled rollover, compromise, or merger of institutions.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
campus identity provider
research federations
cloud and learning services
signing-key overlap and metadata propagation
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Departments and external research services cache metadata differently, turning a key rollover into widespread login failure.
Frame the decision the owners must make
Which relying services will reject a new federation signer, and how quickly can stale metadata be corrected?
Apply QNSI to the controlled boundary
Inventory federation keys, relying parties, metadata refresh, audiences, algorithms, owners, and last verification in QNSI.
Leave the team with a concrete result
A campus federation rollover matrix with test accounts, metadata lag, escalation owners, and retirement proof.
Prove the result in the organisation's environment
The institution tests authentication assurance, accessibility, privacy, emergency login, external partners, and help-desk readiness.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A campus federation rollover matrix with test accounts, metadata lag, escalation owners, and retirement proof.
Independent validation boundary
The institution tests authentication assurance, accessibility, privacy, emergency login, external partners, and help-desk readiness.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.