Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #351963
Closed
Open
Issue created Feb 03, 2022 by Dan Jensen@djensenContributor2 of 2 checklist items completed2/2 checklist items

SSH: Do not allow expiration enforcement to be disabled

Problem to solve

Since #250480 (closed), GitLab allows administrators to disable the enforcement of SSH key expiration. That could cause unexpected behavior for users when the setting is enabled. Specifically, users might not be aware when their credentials (or others') are expired but still in use.

Proposal

We should deprecate and remove the ability for administrators to disable the enforcement of SSH key expiration:

  • Deprecation announcement and documentation update in %14.8. See !79905 (merged)
  • Feature removal in %15.0
    • Admin setting for enforce_ssh_key_expiration
    • Admin documentation

Note: This is a revert of the work done under #250480 (closed).

Edited May 11, 2022 by Max Woolf
Assignee
Assign to
Time tracking