Token is not optional anymore. about node-vault HOT 8 CLOSED

@marcoslopes OK, will have a look at it asap...thanx for finding this issue 👍

from node-vault.

@kr1sp1n no, thank you for the prompt reply! =]

from node-vault.

@marcoslopes Should be fixed now since version 0.5.5
Please verify! Thanks 👍

from node-vault.

@kr1sp1n yeah it works like a charm! thanks heaps for that! 👍

from node-vault.

This broken again? Using userpass authentication. Which seems to succeed, but further calls fail.

node-vault@^0.5.6

Unhandled rejection Error: missing client token
    at handleVaultResponse (node_modules/node-vault/dist/index.js:36:19)
    at tryCatcher (node_modules/request-promise/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (node_modules/request-promise/node_modules/bluebird/js/main/promise.js:510:31)
    at Promise._settlePromiseAt (node_modules/request-promise/node_modules/bluebird/js/main/promise.js:584:18)
    at Promise._settlePromises (node_modules/request-promise/node_modules/bluebird/js/main/promise.js:700:14)
    at Async._drainQueue (node_modules/request-promise/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (node_modules/request-promise/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues (node_modules/request-promise/node_modules/bluebird/js/main/async.js:15:14)
    at runCallback (timers.js:651:20)
    at tryOnImmediate (timers.js:624:5)
    at processImmediate [as _immediateCallback] (timers.js:596:5)

from node-vault.

@dishcandanty Will have a look asap.

from node-vault.

@dishcandanty I tested it and improved the examples in the develop branch.
Here is how it works for me now:

1. Start vault
   docker-compose up --force-recreate vault
2. Initialize vault and copy root_token from the response
   node example/init.js
3. Set env var VAULT_TOKEN
export VAULT_TOKEN=[root_token]
4. Add policy mypolicy
node example/addPolicy.js
5. Enable userpass auth
   node example/enableAuth_userpass.js
6. Login via userpass auth
   node example/userpassLogin.js

It is required that you set vault.token to the client_token value from the login response.
That is at the moment far from perfect. Would be better to set the token automatically after any login strategy (e.g. github etc.).

from node-vault.

Ok, will close this issue for now.

from node-vault.