Data is collected from the institutions participating in the eduroam in that NRO. Exact process is a matter of local implementation in a NRO.

Data is stored in the SQL database on the virtual machine that is operated in the infrastructure provided by SURFNET. The raw data is accessible only by the personnel of eduroam operations team. The virtual machine is maintained by the OT.

System sends emails with invitation tokens (one variant to institution administrators for sign-up, one variant to NRO personnel for general status updates)

• The authorisation status of administrators who ever logged in is retained permanently.
• The installer-relevant information is kept until the administrator chooses to delete it (then deleted immediately).
• There is a cache for previously generated installers which gets invalidated upon deletion of the installer-relevant information (but remains on disk until manual cleanup is triggered).

Deployment details of Managed IdP for NRO (from NRO admin input)

• Whether it is enabled or not
• max number of users per institution profile
• EAP termination settings

Deployment details of Managed IdP for institution

• whether the admin has accepted the system's ToU
• (pseudonymous) usernames of the institution's users
• expiry date of said pseudonymous usernames
• list of eduroam credentials issued to these users (properties of these credentials in 8, below), linked to the respective username
• list of pending invitation tokens with which users can create new credentials and inquire about their account status (properties of invitation toekns in 9, below)
• status of the usernames (active, inactive)
• data freshness: when were the set of users last checked by the administrator for continued validity?

eduroam credentials (X.509 certificates)

• unique, randomly generated username as certificate Subject (original pseudonymous username is not contained, but system maintains an internal link between pseudonymous username and the Subject of the certificate)
• date of issue and expiry of certificate
• unique, randomly chosen serial number for certificate
• device type for which certificate was generated
• revocation status of certificate
• invitation token (see 9, below) which was used to generate certificate

end-user invitation tokens (URLs with unique, random long identifier)

• pseudonymous username to which invitation token pertains
• number of devices which can be credentialed witht his token
• expiry date of invitation token

RADIUS authentication logs

The RADIUS server is an eduroam IdP in the sense of the dataset "eduroam RADIUS server logs → IdP" above, and the same data set considerations apply.

certificate status server logs

• logs the timestamp when a revocation assertion was requested for a given eduroam credential - revocation assertions typically coincide exactly with the actual authentication happening on the RADIUS server. Does not log the actual revocation state that was returned.