Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 562
    • Issues 562
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 70
    • Merge requests 70
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #1421
Closed
Open
Issue created Sep 11, 2020 by Tomek Mrugalski@tomek🛰Owner

Add authentication hook point

As part of the #1304 (closed), @fdupont and I discussed the evolution of the basic http auth evolution. The code introduced in #1304 (closed) adds a basic credentials storage in the Kea config file. However, there are better alternatives envisaged in the future (keep them in a file, in a DB, perhaps in external system, like PAM, LDAP, RADIUS, etc.). Those could be implemented as hooks.

For this reason, we need a hook point that will:

  • expose the credentials provided in a request to be authenticated
  • let the hook decide whether the request should be authenticated or not
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking