...
Target date: Q2 2017
Task 4
Documents:
PID: Draft pending CBA and pilot plan update
CBA:
Roadmap: roadmap-eaas.pdf, - migrate to Shaun's doc.
Service Description: eduroam Managed IdP (external testing)
Service Policy: idem, chapter 2 - update with additional eligibility to use as discussed 16/2
Service Design Documents:
- Original GN4-1 deliverable 9.3
- Roadmap, SW-style
- Client CA - architecture
- Server CA - architecture
- Components and Workflow
...
- basic UAT: validate all steps of workflow
initial signup
manual one user creation
CSV user creation
invitation issuance
installer pickup
eduroam usage
credential expiry /revocation - input regarding various design choices
tracing: how important is it group users across credentials with Chargeable-User-Identity?
product exclusivity: Managed IdP XOR normal RADIUS profiles
import: is the choice "manual" and "import by CSV" sufficient? Which other user upload method would people like?
credential communication: is it okay to leave means of sending invitation token to admin? Shall we implement a "Send by email/Skype/Facebook"?
deadman switch: is this appreciated/its necessity understood? What would be a comfortable interval for participants?
end-user import: is the "one time import password" mechanism understood? If any, what are its UX problems?
OS autodetection: does this work well enough - and do end users "get it" that they should visit the download page with the exact device they want to configure?
re-use of invitations: one invitation, one credential, one device? Or should invitation allow multiple devices, or be good for a certain amount of time for an arbitrary number of devices?
Add Pilot plan text for piloting business model.
KPIS (adapted from GN4-1 D9.3):
...