Readme needs instructions on what variable to pass for authorization_token about bridgely-api HOT 5 CLOSED

Hi @kikuchiyo,

You're right. I don't think I documented authentication well enough for this project. I would update /db/seeds.rb (I just realized much of that configuration is specific to this particular application...) and

At the very least, update the admin account to your own, and the user1 and user2 seeds can stay or go. Then run rake db:reset db:seed

Once you have your accounts in order you can access your login token by sending a POST request to http://localhost:#{som_port}/v1/auth/login/ for example:
curl -X POST -F 'session[email][email protected]' -F 'session[password]=test_password' http://0.0.0.0:3000/v1/auth/login

This will return a response with an authorization token that should be used for all subsequent requests, and allow you to access the other endpoints.

from bridgely-api.

Thanks @nason

from bridgely-api.

@nason, it's giving me back the same authorization_token I had been testing with earlier ( obtained via rails console ). Should I be able to do this ( assuming the correct authorization_token ) or should I pass a differently named parameter?

curl -G -d 'authorization_token=#{my_token_here}' http://localhost:3000/v1/companies/1/employees.json

from bridgely-api.

The authorization token is expected in the request header, so your example won't work but something like this should:
curl -G -H 'Authorization:Token {your_token_here}' http://localhost:3000/v1/companies/1/employees.json

from bridgely-api.

perfect! thanks again @nason

from bridgely-api.