-
Notifications
You must be signed in to change notification settings - Fork 20
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
PowerCommander - Add-KeeperSecretManagerClient can't return base64 configuration string #103
Comments
It looks like this task belongs rather to secrets-manager project then to keeper sdk for .Net. That configuration could be converted to base64 text as
I will transfer this issue to secrets manager repository |
@sk-keeper - I believe this repo was the correct spot for this issue. You are correct that KSM can be used to exchange a one-time token for a base64 configuration. However, I'd like to see that ability added to PowerCommander. Specifically, the In full-fledged Keeper Commander CLI, you can get a base64 config back at the time you add/create a client. For example: I would like that same ability in PowerCommander's |
@rdavisunr It is SecretsManager API that converts one time access token access token into base64 configuration. We do not want to distribute SecretsManager SDK with .Net Keeper SDK/PowerCommander. You mentioned in your original message:
It looks like you already have both SDKs in your setup. You can use already installed SecretsManager SDK to create Base64 configuration from the one time access token. |
@rdavisunr - If you are going to use both SDKs then extending SecretsManager SKD would be the easiest solution. |
The part of the deployment that uses the Secrets Manager PowerShell plugin runs separately and in a different environment from the part that is using PowerCommander to create folders, apps, clients and Terraform for secrets. Ultimately, I was just hoping for feature parity between Keeper Commander CLI and PowerCommander. But, I understand the limitations after your explanation. |
We'll add that missing step (exchange one time token for ksm configuration) into Keeper SDK. It is just one API call. |
PowerCommander v0.9.3 is published to PowerShell Gallery. |
PowerCommander doesn't seem to have the option to return a base64 configuration string when creating a Keeper Secret Manager Client. Only the one time access token is provided as a return value. Example:
Add-KeeperSecretManagerClient -App “someApp”
Whereas, the regular Commader CLI can do the following:
secrets-manager client add --app someApp --config-init b64
Could you please add the ability to create base64 configs in the PowerCommander Add-KeeperSecretManagerClient function?
Alternatively, is there a current method in PowerCommander to convert a one time access token into a base64 config?
Extra Context
I am evaluating the Secret Manager product as a possible purchase add-on for my organization (we are a current Keeper customer).
Here's what I am trying to accomplish:
During an automated Infrastructure Deployment...
The text was updated successfully, but these errors were encountered: