Ryan Treat

Since this is really a technical shortcoming of TPP we'll need to workaround it by treating any `POST /certificates/revoke` response that includes `"Warning"` as an error (revocation failure) even though...

Since this is due to an issue with Go itself, it will require 3rd party assistance. The attempt referenced by https://github.com/golang/crypto/pull/104 (i.e. https://go-review.googlesource.com/c/crypto/+/201457) was abandoned ☹️

Thank you for raising this issue @sitaramkm. This problem is a side effect of TPP's object-based design and does not apply to Venafi as a Service. As such, that gives...

Just to summarize before closing, instead of passing the token on the command line using the `-t` parameter, you can pre-assign the token value to the `VCERT_TOKEN` environment variable or...

Believe this would require significant refactoring. May only be worthwhile in the context of adding support for Java Keystore (jks) format. This issue is related to https://github.com/Venafi/vcert/issues/41.

Reclassifying as an enhancement because the `getcred` action was not designed to support this use case. One of the major reasons that token authentication was introduced in TPP was to...

Thank you for your feedback @stoehdoi. This would actually be an enhancement because permissions were intentionally removed from the policy specification in the original design of the certificate policy management...

@maelvls Yes, you're right this would be an enhancement. We've actually never previously had anyone express interest in Custom Field support for the import use case and since TPP currently...

Added https://community.venafi.com/ideas/custom-field-support-for-post-vedsdk-certificates-import-1017

The link should be accessible to all current Venafi customers. It has not yet been opened up to all internal departments but I believe that is the end goal.