-
-
Notifications
You must be signed in to change notification settings - Fork 140
Description
Describe the feature request or question
I have seen several other issues logged and marked as resolved, but the behavior in the client seems to have changed since those issues. The Hashicorp Vault example repository (https://github.com/hashicorp/hello-vault-dotnet/blob/c47dd2f57a657618385034adf2028f86e3179989/sample-app/WebService/Vault/VaultWrapper.cs#L57) shows passing null to the ...V1.System.UnwrapWrappedResponseDataAsync function and setting the wrapping token in the TokenAuthMethodInfo, but the user is now presented with an error that the token cannot be null in the function call. It seems that there have been additional checks put into place that will not allow the user to unwrap a token unless they are authenticated despite the API documentation show it is possible: https://developer.hashicorp.com/vault/api-docs/system/wrapping-unwrap#sample-request
Is there a particular reason this behavior has changed? Can there be a way to expose the unwrap functionality without requiring auth or using up the wrapping token?
Link to the Vault API Docs that support this feature
The Vault Docs URL
Additional context
The workflow I am looking to accomplish is to have returned SecretIDs seal-wrapped and have my application unwrap the SecretID to then authenticate.