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

SecretManagement install check failing in some circumstances #123

Closed
gdbarron opened this issue Jun 27, 2022 · 0 comments
Closed

SecretManagement install check failing in some circumstances #123

gdbarron opened this issue Jun 27, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@gdbarron
Copy link
Collaborator

Environment

Operating System: Windows 11
VenafiPS version: 4.5.0
PowerShell version: 7.2.4
TPP version (if applicable): 21.3

Steps to reproduce

Ensure the SecretManagement module is not installed. Create a new token session and use -VaultAccessTokenName.

Expected behavior

A new session is created and the access token is stored in the vault

Actual behavior

A new session is created, but this error is received when trying to set the secret.

Set-Secret: /home/user/.local/share/powershell/Modules/VenafiPS/4.5.0/Public/New-VenafiSession.ps1:472
Line |
 472 |          Set-Secret -Name $VaultAccessTokenName -Secret $newSession.To …
     |          ~~~~~~~~~~
     | The term 'Set-Secret' is not recognized as a name of a cmdlet, function, script file, or
     | executable program. Check the spelling of the name, or if a path was included, verify that the
     | path is correct and try again.

Screenshots

@gdbarron gdbarron self-assigned this Jun 27, 2022
@gdbarron gdbarron added the bug Something isn't working label Jun 27, 2022
gdbarron added a commit that referenced this issue Jun 27, 2022
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