From 31cd78745443006e935969b38df7498ab448f60e Mon Sep 17 00:00:00 2001 From: chaosinthecrd <tom@tmlabs.co.uk> Date: Wed, 26 Jul 2023 16:21:34 +0100 Subject: [PATCH 1/3] adding further description of KeyManager Signed-off-by: chaosinthecrd <tom@tmlabs.co.uk> --- content/docs/latest/planning/extending.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/docs/latest/planning/extending.md b/content/docs/latest/planning/extending.md index f0487ba3..33045f23 100644 --- a/content/docs/latest/planning/extending.md +++ b/content/docs/latest/planning/extending.md @@ -53,6 +53,8 @@ In some cases it might be desirable for SPIRE to avoid being exposed to a signin SPIRE comes with a set of built-in Key Manager plugins for the [Server](/docs/latest/deploying/spire_server/) and [Agent](/docs/latest/deploying/spire_agent/). +Note that the Key Manager is *not* provided with contextual metadata about the signing operation that it is performing (e.g., X.509 Certificate Signing Request). The SPIRE server performs any necessary policy evaluation on the signing request itself, and hands hashed data to the Key Manager plugin that is used as an input for creating a signature. This means that a Key Manager plugin cannot be developed for the means of performing evaluation of the request outside of the SPIRE server (e.g., Certificate Authority (CA) service in the case of X.509). The Upstream Authority plugin is the single method of integration between SPIRE and external CA's. + # Notifier plugins Notifier plugins allow actions to be triggered in other systems when certain events occur on the SPIRE Server, and in some cases interrupt the event itself. Notifier plugins can support a number of different use cases, such as when certificate rotation events occur. From 97f9a323cf515b7fc395e38ffef2c3d1c41f39f4 Mon Sep 17 00:00:00 2001 From: chaosinthecrd <tom@tmlabs.co.uk> Date: Wed, 26 Jul 2023 16:35:55 +0100 Subject: [PATCH 2/3] bolding Signed-off-by: chaosinthecrd <tom@tmlabs.co.uk> --- content/docs/latest/planning/extending.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/latest/planning/extending.md b/content/docs/latest/planning/extending.md index 33045f23..6297bde1 100644 --- a/content/docs/latest/planning/extending.md +++ b/content/docs/latest/planning/extending.md @@ -53,7 +53,7 @@ In some cases it might be desirable for SPIRE to avoid being exposed to a signin SPIRE comes with a set of built-in Key Manager plugins for the [Server](/docs/latest/deploying/spire_server/) and [Agent](/docs/latest/deploying/spire_agent/). -Note that the Key Manager is *not* provided with contextual metadata about the signing operation that it is performing (e.g., X.509 Certificate Signing Request). The SPIRE server performs any necessary policy evaluation on the signing request itself, and hands hashed data to the Key Manager plugin that is used as an input for creating a signature. This means that a Key Manager plugin cannot be developed for the means of performing evaluation of the request outside of the SPIRE server (e.g., Certificate Authority (CA) service in the case of X.509). The Upstream Authority plugin is the single method of integration between SPIRE and external CA's. +Note that the Key Manager is **not** provided with contextual metadata about the signing operation that it is performing (e.g., X.509 Certificate Signing Request). The SPIRE server performs any necessary policy evaluation on the signing request itself, and hands hashed data to the Key Manager plugin that is used as an input for creating a signature. This means that a Key Manager plugin cannot be developed for the means of performing evaluation of the request outside of the SPIRE server (e.g., Certificate Authority (CA) service in the case of X.509). The Upstream Authority plugin is the single method of integration between SPIRE and external CA's. # Notifier plugins From 789297ee3b3d2fac86347cfc51cead49f7faa6b1 Mon Sep 17 00:00:00 2001 From: Tom Meadows <tom@tmlabs.co.uk> Date: Thu, 24 Aug 2023 09:44:18 +0100 Subject: [PATCH 3/3] Update content/docs/latest/planning/extending.md Co-authored-by: Steve Anderson <steve.anderson@hpe.com> Signed-off-by: chaosinthecrd <tom@tmlabs.co.uk> --- content/docs/latest/planning/extending.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/latest/planning/extending.md b/content/docs/latest/planning/extending.md index 6297bde1..a669b3b2 100644 --- a/content/docs/latest/planning/extending.md +++ b/content/docs/latest/planning/extending.md @@ -53,7 +53,7 @@ In some cases it might be desirable for SPIRE to avoid being exposed to a signin SPIRE comes with a set of built-in Key Manager plugins for the [Server](/docs/latest/deploying/spire_server/) and [Agent](/docs/latest/deploying/spire_agent/). -Note that the Key Manager is **not** provided with contextual metadata about the signing operation that it is performing (e.g., X.509 Certificate Signing Request). The SPIRE server performs any necessary policy evaluation on the signing request itself, and hands hashed data to the Key Manager plugin that is used as an input for creating a signature. This means that a Key Manager plugin cannot be developed for the means of performing evaluation of the request outside of the SPIRE server (e.g., Certificate Authority (CA) service in the case of X.509). The Upstream Authority plugin is the single method of integration between SPIRE and external CA's. +Note that the Key Manager is **not** provided with contextual metadata about the signing operation that it is performing (e.g., X.509 Certificate Signing Request). The SPIRE Server performs any necessary policy evaluation on the signing request itself, and hands hashed data to the Key Manager plugin that is used as an input for creating a signature. This means that a Key Manager plugin cannot be developed to evaluate the request outside of the SPIRE Server (e.g., Certificate Authority (CA) service in the case of X.509). The Upstream Authority plugin is the single method of integration between SPIRE and external CAs. # Notifier plugins