Skip to content
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

Initialize-TssSdkClient - issue using onboarding key does not initialize #84

Closed
wsmelton opened this issue Feb 22, 2021 · 1 comment
Closed
Assignees
Labels
bug Something isn't working

Comments

@wsmelton
Copy link
Contributor

Reported by @PatrickV-code

VERBOSE: Provided command parameters: Initialize-TssSdkClient
-SecretServer:'https://url' -RuleName:'applicationsdk'
-OnboardingKey:'s1PsQ4YuL0Ysgm' -ConfigPath:'H:\sdk-powershell\' -Force:$True
-Verbose:$True
VERBOSE: arguments for tss init: remove --confirm --key-directory H:\sdk-powershell\ --config-directory
H:\sdk-powershell\
VERBOSE: SDK Client raw output: Your configuration settings have been removed.
VERBOSE: SDK Client configuration has been removed
VERBOSE: arguments for tss init: init --url https://url --rule-name applicationsdk
--onboarding-key 's1PsQ4YuL0Ysgm' --key-directory H:\sdk-powershell\ --config-directory
H:\sdk-powershell\
VERBOSE: SDK Client raw output: 400 - Bad Request
@wsmelton wsmelton added the bug Something isn't working label Feb 22, 2021
@wsmelton wsmelton added this to the 0.5 Release milestone Feb 22, 2021
@wsmelton wsmelton self-assigned this Feb 22, 2021
@wsmelton
Copy link
Contributor Author

Single-ticks for some reason cause issue when calling tss.exe, even though doing it via console works fine. Tested and removing those from the onboarding key resolves the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant