Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • Aegir HTTPS Aegir HTTPS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • AegirAegir
  • Aegir HTTPSAegir HTTPS
  • Issues
  • #10
Closed
Open
Issue created Nov 18, 2016 by Christopher Gervais@ergonlogicOwner

Add a 'manual' Certificate implementation

We should add the ability to paste a CA certificate into the front-end. It should presumably look something like:

AWS_SSLCertificate

Ideally we'd also:

  1. Generate the key/CSR.
  2. Validate the certs(s) in the front-end.
  3. Expunge the key from the front-end DB.
  4. Notify when a certificate is coming due for renewal (this could be implemented as a hosting_probe)

For background, see #2 (closed).

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