idimov-keeper

Try adding `params:` in the `spec:` section ``` mount: ksm path: record params: uid: "_SecretUID_" ```

This feature request will be implemented in the next release - addressing a limitations of API Explorer which can work only with path parameters. You can use [PR#505](https://github.com/Keeper-Security/secrets-manager/pull/585) to track...

[vault-plugin-secrets-ksm v1.0.3](https://github.com/Keeper-Security/secrets-manager/releases/tag/vault-plugin-secrets-ksm%2Fv1.0.3) release addresses these issues (by providing path parameters)

KSM CLI [1.1.4](https://github.com/Keeper-Security/secrets-manager/releases/tag/ksm-cli-1.1.4) added `ksm secret delete` command

These issues have been resolved with the release of KSM CLI 1.1.3 download [here](https://github.com/Keeper-Security/secrets-manager/releases/tag/ksm-cli-1.1.3) check the release notes [here ](https://github.com/Keeper-Security/secrets-manager/tree/master/integration/keeper_secrets_manager_cli#113)

Try setting token without quotes an without surrounding chars - tokens are either 43 or 46 (incl. host prefix) characters long and the error says that your token is 45...

How are you generating your tokens? Your token is missing a padding character at the end. Try appending equal sign at he end ('=' without quotes) for a quick test....

We found a bug in KSM CLI tool that's preventing the use of `KSM_TOKEN` environment variable. We are working on a fix. As a workaround currently you can use `--token`...

In the next release KSM CLI 1.1.6 we introduce new env variable **KSM_CLI_TOKEN** that works the same way as **KSM_TOKEN** but allows you to use command line options for the...

Folder management is on the roadmap but still work in progress. Secrets manager clients and SDKs will start adding new features as soon as back-end release with KSM folder management...