What
Opening a node detail page (/nodes/<name>) for a node in the awaiting-cert state (a freshly adopted subordinate that has not yet been signed) errors out. Once the node is established (has an identity/cn/chain) the page loads fine, so the failure is specific to the no-identity window.
Repro
Adopt a subordinate (it lands at awaiting-certificate), then click it on /nodes before completing its enrollment.
Notes
fromSummary and NodeDetailPanel render a full field set with defaults, and useCerts degrades gracefully, so the throw is likely in a child that assumes an identity/cn/chain during the awaiting-cert window. Needs the browser console error (or an awaiting-cert repro) to pin the exact line; then guard the no-identity case (render the panel with placeholders instead of throwing).
Surfaced during the live two-tier ACME build. Part of CryptOS-PKI/manager#24.
What
Opening a node detail page (
/nodes/<name>) for a node in theawaiting-certstate (a freshly adopted subordinate that has not yet been signed) errors out. Once the node is established (has an identity/cn/chain) the page loads fine, so the failure is specific to the no-identity window.Repro
Adopt a subordinate (it lands at awaiting-certificate), then click it on
/nodesbefore completing its enrollment.Notes
fromSummaryandNodeDetailPanelrender a full field set with defaults, anduseCertsdegrades gracefully, so the throw is likely in a child that assumes an identity/cn/chain during the awaiting-cert window. Needs the browser console error (or an awaiting-cert repro) to pin the exact line; then guard the no-identity case (render the panel with placeholders instead of throwing).Surfaced during the live two-tier ACME build. Part of CryptOS-PKI/manager#24.