\o As promised (though, late!), here's the ACL policies I was thinking about. I've linked to our tutorial about configuring an ACL policy for instructions on provisioning it, though note that this depends on the auth method used (for linking token creation to specific policies).
One comment: Vault 1.15 is right around the corner, and with it comes the mentioned X509 support within Transit. As this plugin isn't yet released, it seems like it might be a good time to drop the dependency on KVv2 and instead rely just on Transit. Happy to provide a PR if desired.
(Also, I was noticing that it seems like the path to Transit or KV aren't configurable -- is there a pattern for providing configuration information to plugins? A lot of customers won't use a fixed transit in the root namespace).
\o As promised (though, late!), here's the ACL policies I was thinking about. I've linked to our tutorial about configuring an ACL policy for instructions on provisioning it, though note that this depends on the auth method used (for linking token creation to specific policies).
One comment: Vault 1.15 is right around the corner, and with it comes the mentioned X509 support within Transit. As this plugin isn't yet released, it seems like it might be a good time to drop the dependency on KVv2 and instead rely just on Transit. Happy to provide a PR if desired.
(Also, I was noticing that it seems like the path to Transit or KV aren't configurable -- is there a pattern for providing configuration information to plugins? A lot of customers won't use a fixed transit in the root namespace).