## Overview Admin Area page to add, list, and remove instance-level trusted CAs. This is the piece GitLab Dedicated actually needs — Dedicated tenants have Admin Area access but no filesystem access, so this is their only route to configuring instance-wide SSH certificate authentication. Consumes the API from #611314. ## Reference implementation Admin Deploy Keys is the closest existing pattern — an instance-level list of keys with add and delete. Follow its structure: | Concern | Deploy keys equivalent | |---------|------------------------| | Controller | `app/controllers/admin/deploy_keys_controller.rb` | | Route | `config/routes/admin.rb` | | Index view | `app/views/admin/deploy_keys/index.html.haml` | | Vue table | `app/assets/javascripts/admin/deploy_keys/components/table.vue` | | Page entry | `app/assets/javascripts/pages/admin/deploy_keys/index/index.js` | | Sidebar menu | `lib/sidebars/admin/menus/deploy_keys_menu.rb` | The established split is a Vue-rendered list mounted in a minimal HAML index, with a server-rendered HAML form for the add flow. ## Proposal ### 1. Controller and route `Admin::SshCertificatesController < Admin::ApplicationController` with `index`, `new`, `create`, `destroy`. Admin authentication and the admin layout are inherited from the base controller, so no explicit `authorize!` is needed. Add an availability gate, following `Admin::HooksController`, which uses the same approach to hide a page that does not apply on GitLab.com: ```ruby before_action :not_found, unless: -> { InstanceSshCertificate.available? } ``` Route in `config/routes/admin.rb`: ```ruby resources :ssh_certificates, only: [:index, :new, :create, :destroy] ``` No `edit`/`update` — a CA key is immutable. Changing one means deleting and re-adding, which is also the correct semantics for revocation. ### 2. Index view and Vue list Minimal HAML mount point, as with deploy keys: ```haml - page_title _('SSH certificates') = render ::Layouts::PageHeadingComponent.new(_('SSH certificates')) #js-admin-ssh-certificates-table ``` Vue component displaying `title`, fingerprint, and created-at per row, with pagination, an empty state, a "New certificate" button, and a delete confirmation modal. Data comes from `GET /api/v4/admin/ssh_certificates`. Show the fingerprint rather than the raw key — it is what admins compare against their CA, and what appears in logs and audit events. ### 3. Add form Server-rendered HAML form with `title` and `key` fields, posting to `create`. The controller calls `InstanceSshCertificates::CreateService` from #611314 and surfaces validation errors inline — including the FIPS key-strength rejections, which need a comprehensible message rather than a raw validator error. ### 4. Delete confirmation The modal must state that removing a CA revokes trust immediately and that any certificates it signed stop working at once. This is the feature's only revocation mechanism, so it needs to be explicit to admins rather than implied. ### 5. Sidebar Add `lib/sidebars/admin/menus/ssh_certificates_menu.rb` following `DeployKeysMenu`, and register it conditionally in `lib/sidebars/admin/panel.rb` so it does not render when `InstanceSshCertificate.available?` is false — matching how the System Hooks menu is conditionally added. ## Design proposal See https://gitlab.com/gitlab-org/gitlab/-/work_items/611319#note_3828496877. Note that navigation updates will be made in #628272. [:art: Figma](https://www.figma.com/design/eq2nf3B8MhB9xKrC0VzbPf/branch/mC8PodcCRABxwyR9ncnTQh/Repository?m=auto&node-id=10094-9160&t=5xNQ34GVhlf0nn7Q-1) <table> <tr> <th></th> <th>Screen</th> </tr> <tr> <td>SSH certificates page</td> <td> {width="900" height="512"} {width="900" height="512"} * Navigation updates in https://gitlab.com/gitlab-org/gitlab/-/work_items/628272 * Create new nav category `Access` * Create new page `SSH certificates` * Move `Credentials` `Deploy keys` `SSH certificates` under `Access` nav category * `Copy` button: Copies the fingerprint * Hover text: `Copy fingerprint` * Toast text: `Fingerprint copied to clipboard.` * `View details` menu item: Allows users to view the full public key as needed. Less frequent action hidden in the overflow menu. * `Delete` menu item: Deletes the CA. Less frequent and destructive action hidden in the overflow menu. * Toast text: `Certificate authority deleted.` </td> </tr> <tr> <td>Add new</td> <td> {width="797" height="600"} * Toast text: `Certificate authority added.` </td> </tr> <tr> <td>View details</td> <td> {width="797" height="600"} * Fingerprint is visible * Public key description has additional text </td> </tr> <tr> <td>Empty state</td> <td> {width="900" height="512"} </td> </tr> <tr> <td>Pagination</td> <td> {width="900" height="512"} * If there are more than 10 items in the list, display pagination. While the standard for overflow is generally 20 items for GitLab elements, showing 20 elements in the CRUD component takes up a significant amount of screen real estate. </td> </tr> </table> ## Acceptance criteria - [ ] Admin can list, add, and delete instance CAs from the Admin Area. - [ ] Page and routes return 404 on GitLab.com and when the feature flag is off. - [ ] Sidebar entry is hidden when the feature is unavailable. - [ ] Non-admin users cannot reach the page. - [ ] List shows title, fingerprint, and created-at, with pagination and an empty state. - [ ] Invalid or non-FIPS-compliant keys produce a clear inline error. - [ ] Delete confirmation states that trust is revoked immediately. - [ ] Feature specs cover add, list, delete, and the unavailable case. - [ ] Frontend unit tests for the Vue component. ## Out of scope - Audit events for create and delete — separate issue. - Editing an existing CA. - Any enforcement setting, such as requiring certificate authentication or disabling personal SSH keys. ## Links - Epic: gitlab-org&amp;22743 - Depends on: #611314 - Group-level equivalent (never built): #421539 - Reference: `app/controllers/admin/deploy_keys_controller.rb` and `app/assets/javascripts/admin/deploy_keys/`