[FEATURE REQUEST] Additional "Notes" field as dynamic value

[hmmmfctunlpt]

It would be nice to have an optional extra field (notes?) to enter additional information per certificate.
Besides the possible extra tagging, it could allow additional information aggregation to the certificate, like defining a clients technical contact to be used in post processing.

[gregtwallace]

Can you use the existing description field? It is essentially a field you can store any data you want in it, as it isn't used in any meaningful way beyond displaying to human operators.

[hmmmfctunlpt]

Hello Greg,

Yes, I'm aware of the description field, and my suggestion for a "notes" was so that one wouldn't have to loose the ability to also have a description. Even if one takes that approach, that field is still not useable for post processing, which was the main goal.

After giving it some thought, I actually believe it would be beneficial to include a couple of well defined fields for tech contacts (non mandatory), having them available for post processing scripts.

Just like one can now use

{{PRIVATE_KEY_NAME}} - The name of the private key that corresponds to the new certificate.
{{PRIVATE_KEY_PEM}} - The actual PEM data of the private key.
{{CERTIFICATE_NAME}} - The name of the certificate.
{{CERTIFICATE_PEM}} - The actual PEM data of the newly issued certificate.
{{CERTIFICATE_COMMON_NAME}} - The CN of the newly issued certificate.

I would suggest adding new

{{TECH_EMAIL}} - The technical contact email for the certificate.
{{TECH_PHONE}} - The technical contact phone number for the certificate.

And also making the API KEYS available as dynamic variables, like

{{CERTIFICATE_API_KEY}} - The API access KEY for the certificate.
{{PRIVATE_KEY_API_KEY}} - The API access KEY for the certificate private key.

Not only it would allow a (contained) finer grain control on the life cycle of the certificate but also allow automatic notifications uppon certificate issuing/renewal, either via email or an SMS gateway for example.

In my particular case it would allow to automate user certificate/key self checkout, respective API keys and specific user instructions, with possibility to even use 2FA, without having to grant them access to certwarden.

Thanks.

[hmmmonteiro]

Greetings, Greg.

Please take some moments to review and consider merging both PRs certwarden-frontend PR#8 and both certwarden-backend PR#19 and certwarden-backend PR#20.

Thanks in advance.