Fetching secrets from an empty vault fails about secrets-manager HOT 6 CLOSED

Hello ivankustera
Example code should work with both localConfigStorage and loadJsonConfig.

What is your Node version?
What is the version of Keeper Secrets Manager JavaScript SDK?
"@keeper-security/secrets-manager-core": "^16.3.1",

A few suggestions that may help in resolving the issue:

1. Try using absolute path for the config file.
2. Debug print the JSON text before loading it into loadJsonConfig to make sure appKey is present - you should see a line like this: "appKey": "xXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXx=",

...
	const configJson = require('fs').readFileSync('./ksm-config.json').toString()
	console.log(configJson)
	const storage = loadJsonConfig(configJson)
...

Please do not post actual config file contents in this thread.

from secrets-manager.

Hi,

I have verified that config file and string I am passing to loadJsonConfig have all needed keys. This config was produced by the following CLI command:

secrets-manager client add --app MyApp --config-init json --unlock-ip

Also, I added some logging into storage's getValue and getBytes methods and I can see that at some point it gets value for appKey but later it fails. So the storage is at least initialised with it.

My node version is v16.13.0 and the sdk is "@keeper-security/secrets-manager-core": "^16.3.1".

from secrets-manager.

from secrets-manager.

Thanks for your reply, but I am still having troubles to make it work. Here are all the details:

node v16.13.0
@keeper-security/secrets-manager-core: "^16.3.1"
Keeper Commander v16.6.6 (Current version)
Python Version: 3.9.13

Here's the helper code:

const oneTimeToken = 'xxx'
module.exports.getKeeperRecords2 = async () => {
  const storage = localConfigStorage("ksm-config-2.json")

  await initializeStorage(storage, oneTimeToken)

  const { records } = await getSecrets({ storage: storage })
  console.log({records})
}

The initial run is fine, I get empty array as expected. But the next run fails with the error:

/Users/ivan/keeper-poc/node_modules/@keeper-security/secrets-manager-core/dist/index.cjs.js:266
        throw new Error(`Unable to load the key ${keyId}`);
              ^

Error: Unable to load the key appKey
    at /Users/ivan/keeper-poc/node_modules/@keeper-security/secrets-manager-core/dist/index.cjs.js:266:15
    at Generator.next (<anonymous>)
    at /Users/ivan/keeper-poc/node_modules/@keeper-security/secrets-manager-core/dist/index.cjs.js:54:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/ivan/keeper-poc/node_modules/@keeper-security/secrets-manager-core/dist/index.cjs.js:50:12)
    at loadKey (/Users/ivan/keeper-poc/node_modules/@keeper-security/secrets-manager-core/dist/index.cjs.js:257:37)
    at /Users/ivan/keeper-poc/node_modules/@keeper-security/secrets-manager-core/dist/index.cjs.js:360:23
    at Generator.next (<anonymous>)
    at /Users/ivan/keeper-poc/node_modules/@keeper-security/secrets-manager-core/dist/index.cjs.js:54:71
    at new Promise (<anonymous>)

I verified that the config generated using one time token was identical as the one that was initialised from the commander.

from secrets-manager.

After a short consultation with Max we figured out the the issue is an empty vault. When I added an empty secret it worked immediately. I am renaming this issue to be more clear what the problem is.

from secrets-manager.

@ivankustera thank you working with us and trying to get to bottom of this issue. We will try to fix this issue soon and also will add a better error messaging.

from secrets-manager.