Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 508
    • Issues 508
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 50
    • Merge requests 50
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #1421

Closed
Open
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