Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A auth
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • id
  • auth
  • Issues
  • #12
Closed
Open
Created Feb 26, 2021 by ale@aleOwner5 of 5 tasks completed5/5 tasks

WebAuthN support

The current U2F implementation will eventually become obsolete, we need to support WebAuthN/FIDO/etc. Unfortunately this requires finding another library to deal with the primitives other than github.com/tstranex/u2f, and it will have to support both U2F and WebAuthN.

This issue tracks implementation across all the components of the stack:

  • ai3/go-common for the U2FRegistration type (ai3/go-common!32 (merged))
  • id/auth for the server-side login workflow (!34 (merged))
  • id/sso-server for the client-side login workflow (sso-server!8 (merged))
  • ai3/pannello for the registration workflow (ai3/pannello!51)
  • ai3/accountserver (ai3/accountserver!42 (merged))
Edited Dec 04, 2021 by ale
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking