-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Support AccessToken auth for Venafi TPP #3140
Copy link
Copy link
Closed
Labels
area/venafiIndicates a PR directly modifies the Venafi Issuer codeIndicates a PR directly modifies the Venafi Issuer codekind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Metadata
Metadata
Assignees
Labels
area/venafiIndicates a PR directly modifies the Venafi Issuer codeIndicates a PR directly modifies the Venafi Issuer codekind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Is your feature request related to a problem? Please describe.
Currently for TPP cert-manager only supports username/password auth. This will
be deprecated in TPP 21.1 and we should switch to AccessToken auth.
Describe the solution you'd like
Extend support to prefer reading AccessToken from the TPP issuer secret if
it is present, fall back to username/password if it is not present.
The docs should be updated to first explain how to set up the AccessToken
method.
Describe alternatives you've considered
I guess it's possible the TPP issuer config should change to be able to
point to a different secret for AccessToken, but I don't see why that would
be needed.
/kind feature