Removed blurb about Key Manager from PR 285

spiffe · Apr 19, 2024 · f9b1afc · f9b1afc
1 parent d011ae4
commit f9b1afc
Showing 1 changed file with 0 additions and 2 deletions.
diff --git a/content/docs/latest/planning/extending.md b/content/docs/latest/planning/extending.md
@@ -51,8 +51,6 @@ Notifier plugins allow actions to be triggered in other systems when certain eve
 
 SPIRE comes with a set of built-in Notifier 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 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.
-
 # Working with first-party plugins
 
 First party plugins can be enabled by including the appropriate configuration stanza in the `plugins` section of the Server or Agent configuration file.