Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Certificator CA Certificator CA
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • TurrisTurris
  • SentinelSentinel
  • Certificator CACertificator CA
  • Issues
  • #13
Closed
Open
Issue created Jan 24, 2020 by Vojtech Myslivec@vmyslivecContributor

Validity period for requests

Implement some validity period for requests from Cert-API. I.e. include timestamp of the request in the queue and do not generate a certificaet for a device when the request is older than several tens of seconds.

The Certgen client give-up the request in 30-40 seconds anyway and every request could potentially generates a new certificate. If the CA process stuck or anything similar gets wrong, there are lot of useless requests in the queue and CA generates a unusable certificates in the db.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking