Descriptive Title1ActorsActors from multiple organizations?Is registration of RPs required?Mobile Authentication?2Information required by RP (including non-identity)?Permission revocation required?Consent required?Software operated locally or SaaS?Developed locally? Language and IDE?
1Provision of K-12 services using OIDC claims without a gateway

K-12 students

Eventually yes; currently only one IdP No     
2OAuth2 authentication for APIs / web servicesApp developers, end-usersYes No     
3IdP authentication using Google or Facebook credentialsEnd-usersNo No     
4Authentication for Nginx / Node.js based applicationsApp developersYes No     
5Provision of services authenticating via OIDC without a gatewayResearchersYes No     
6Authorization by students to release information (e.g., class schedules, debit card balances) to other applicationsStudentsNo Yes     
7Mobile access to medical contact informationPhysiciansNo Yes     
8Mobile access to HIPAA covered patient informationPhysiciansNo Yes     
9Mobile API access to whitepagesEnd-usersYes at some institutions Yes     
           
           

Notes

  • 1 - Titles will be links to full descriptions on separate pages.
  • 2 - "No" means "not mentioned in the use case description."

 

Related Presentations and Articles

 

  • No labels