You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document tracks the Clavis integration in Aurora Portal. The initial backend and UI pieces are implemented, and this note is meant to evolve as the feature grows.
4
+
5
+
## Current Scope
6
+
7
+
The feature currently covers project-scoped management of private certificate authorities (PCAs):
8
+
9
+
- list certificate authorities for a project
10
+
- create a certificate authority
11
+
- delete a certificate authority
12
+
- import a certificate chain for a CA
13
+
- list certificates issued by a certificate authority
14
+
- fetch certificate authority and certificate details by id
15
+
- create certificates under a certificate authority
16
+
17
+
## Implemented UI
18
+
19
+
The active UI entry point is the project service route at `/projects/$projectId/services/pca/`.
20
+
21
+
Implemented screens and interactions:
22
+
23
+
- PCA list page with loading, error, and empty states
24
+
- primary action to create a certificate authority
25
+
- row action menu with delete certificate authority
26
+
- create modal with FQDN/common name validation
27
+
- delete modal with explicit confirmation by typing `delete`
28
+
- CA details page at `/projects/$projectId/services/pca/$pcaId/` via `PcaDetailsView`
29
+
- details page shows CA metadata, certificate validity, CSR content, and delete action
30
+
- details-page delete flow reuses the shared delete modal and redirects back to the PCA list after success
31
+
32
+
The list page currently renders the CA state, id, and common name. It also shows the translated empty state when no PCAs are available for the current project.
33
+
34
+
## Implemented BFF
35
+
36
+
The PCA router is project-scoped and talks to the OpenStack PCA / Clavis service.
All endpoints expect `project_id` in the request context or input and use the OpenStack service client exposed by the Aurora BFF.
50
+
51
+
## Data Model Notes
52
+
53
+
Relevant PCA states are:
54
+
55
+
-`CREATING`
56
+
-`AWAITING_CERTIFICATE`
57
+
-`READY`
58
+
-`FAILED`
59
+
-`UNEXPECTED`
60
+
61
+
A newly created CA starts in `CREATING`. Once its CSR is generated, it moves to `AWAITING_CERTIFICATE`. Importing the certificate chain transitions it to `READY`, at which point it can issue end-entity certificates.
62
+
63
+
The CA schema also includes:
64
+
65
+
-`configuration.subject.common_name`
66
+
-`csr`
67
+
-`certificate`
68
+
-`certificate_chain`
69
+
-`imported_certificate_chain`
70
+
-`project_id`
71
+
72
+
## UX and Validation
73
+
74
+
The create flow currently validates the common name as an FQDN-style value. The delete flow requires a typed confirmation to reduce accidental removal of a CA and its associated certificates.
75
+
76
+
Error states are surfaced directly in the modal or list view when the BFF call fails.
77
+
78
+
## Next Areas To Document
79
+
80
+
The backend already exposes certificate and import operations, but the UI does not yet have dedicated screens for:
81
+
82
+
- certificate list view
83
+
- certificate detail view
84
+
- certificate import flow
85
+
- list filtering, sorting, and search controls
86
+
87
+
Those can be documented once the corresponding UI work lands.
0 commit comments