Description of Issue
The Certificate "Origin" attribute adds an additional piece of metadata that we are starting to track for every certificate request. The purpose is to provide Venafi administrators data about which applications in their organization are making certificate requests.
The “Origin” named parameter was introduced in Venafi Trust Protection Platform v19.4 so it will apply for that version and higher (and will be silently ignored by earlier versions).
The standard naming convention for Origin shall be the VendorName and ProductName (unless VendorName=ProductName or it is a vendor-less open source project in which case it should simply be the ProductName). The goal of this standard is to uniquely identify the integration while keeping the cardinality of Origin as low as possible. Therefore, please do not include the product version or any other information that will change over time as that will make licensing and reporting more challenging.
If you have any questions at all or would like to discuss, just let me know.
Setup
I am happy to provide access to documentation, a Venafi testing instance, as well as be available for any questions that might arise during the development and testing.
Description of Issue
The Certificate "Origin" attribute adds an additional piece of metadata that we are starting to track for every certificate request. The purpose is to provide Venafi administrators data about which applications in their organization are making certificate requests.
The “Origin” named parameter was introduced in Venafi Trust Protection Platform v19.4 so it will apply for that version and higher (and will be silently ignored by earlier versions).
The standard naming convention for Origin shall be the VendorName and ProductName (unless VendorName=ProductName or it is a vendor-less open source project in which case it should simply be the ProductName). The goal of this standard is to uniquely identify the integration while keeping the cardinality of Origin as low as possible. Therefore, please do not include the product version or any other information that will change over time as that will make licensing and reporting more challenging.
If you have any questions at all or would like to discuss, just let me know.
Setup
I am happy to provide access to documentation, a Venafi testing instance, as well as be available for any questions that might arise during the development and testing.