Support for developer long-lived access tokens as means of authentication?

[mecampbellsoup]

https://www.bitgo.com/api/#access-tokens

Is there a method for authenticating using access tokens instead of email/password/OTP?

Happy to contribute to this library if not. 😸

[SimonPotier]

Im very interested to heard more about this too.

[mecampbellsoup]

@simm19 I ended up just doing this:

# Setup the Bitgo Express proxy
BITGO_API = Bitgo::V1::Api.new("http://127.0.0.1:3080/api/v1")

bitgo_token = Rails.application.secrets.fetch :bitgo_access_token

BITGO_API.session_token = bitgo_token

This allows me to use my long-lived developer token as an Authorization Bearer header in each request.

I forked this gem actually to clean up some things, here's where that logic takes place in my fork.

[SimonPotier]

Thank you for your answer, i'll take a look on your fork.

[SimonPotier]

@mecampbellsoup
I have troubles with the original gem,
bitgo appear in gem list, gemfile, bundled correctly, but still i get "uninitialized constant Bitgo" with api = Bitgo::V1::Api.new(Bitgo::V1::Api::TEST) on my rails console.
Did i missed something ?
Thanks

[mecampbellsoup]

Look at the source code. I don't think that Bitgo::V1::Api::TEST constant is actually defined in the gem, you need to initialize the client with a String.