-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Username with $ fails on Windows #421
Comments
Hi @jdrom , thank you for reaching out Could you provide a template of what you were trying to do? Like are you using VCert CLI? VCert SDK? VCert Playbook? Which platform are you trying to reach (TLPSDC p.k.a TPP, TLSPC p.k.a. VaaS)? Version of the VCert software? Edit: Side question, any reason why are you not using Token Auth in case you are using TPP? |
I'm inclined to say I'm accessing TPP using vcert.exe version 5.3.0 which is running a playbook based upon sample.capi.yaml. I believe I am using token auth as I generated a token (ran vcert getcred) to put in the playbook. Sorry that I don't really know all the acronyms you mentioned as I'm not the owner of our Venafi platform. The error output is below, the step prior to this is "retrieving certificate from CAPI Store" that I've omitted. The "~1" in the path of the error messages is how it shows, which is not my username.
|
Hi @jdrom , Could you also provide the following?
|
I was told we're on TPP version 23.1. Effectively using the default template: https://github.com/Venafi/vcert/blob/master/examples/playbook/sample.capi.yaml. Commented out trustBundle and put in my API token. My end goal is for it to update the bindings for WinRM and Remote Desktop. I've sorted out how to handle that with PowerShell script being called via afterInstallAction along with adding setEnvVars:["thumbprint"] into the certificateTasks so that I can pass the newly created certificate's thumbprint to the script. It's really just this weird bug where it's trying to run the scripts from TEMP and doesn't seem to like that the path has a "$" in it due to my Windows username having a "$". The same playbook works fine on other environments where my Windows username does not contain a "$". |
Hey @jdrom, I believe this issue has something to do with the character escaping. I think I see now after reading the log output above a bit closer. I have an idea of where the issue is.. let me do some testing and get back to you here. Edit: No need to upload the playbook.. I got it ;) |
@jdrom @BeardedPrincess has this issue been resolved? does VCert needs fix? |
Yes, this still needs to be investigated / resolved. Let's keep this one open for now @rvelaVenafi |
Likely an edge case, but I was trying to run vcert on a Windows server where my username includes "$" in it (an odd company standard but it is what it is). This results in what appears to be PowerShell failures as I presume the $ isn't properly escaped somewhere in the source code. As such, no certificate is requested or imported.
I believe it's from the TMP/TEMP environment variable, as if I modify this before running to something like C:\temp, instead of the default C:\Users$Name\AppData\Local\Temp, vcert does run successfully.
Should be able to reproduce by creating a local Windows user with "$Name" as the username, and attempting to run vcert as that user while logged in.
The text was updated successfully, but these errors were encountered: