Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
edentata
edentata
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Hemio e. V.
  • edentataedentata
  • Issues
  • #29

Closed
Open
Opened Jun 27, 2017 by Fuchsi*@exampleOwner0 of 3 tasks completed0/3 tasks

usability of key + certificate replacement process

replacing my out-of-date certificates was more trouble than I anticipated. Partially because of #28 , but also because of some minor things that should be relatively easy to fix:

  • creating a new HTTPS configuration should lead to the "HTTPS Configuration" screen after giving it a name instead of the "Website" screen
  • supplying a new certificate should activate the corresponding https configuration per default (or at least offer this as a checkbox option)

And finally (may not be as easy to fix)

  • a notification email about https certificates that are about to run out would be really nice =)
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: hemio/edentata#29