5 ms·

Please open up a discussion on Livebook repo? We would love to understand more what is missing here. :)

anonyfox 3y ago
I slightly complain a single time for the last few years, and jose directly chimes in with kind words immediately. You rock, honestly! But on the topic: I think its a simple problem ultimately, the SF Api (https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm https://developer.salesforce.com/docs/atlas.en-us.api_rest.m...) needs OAuth, which needs a redirect at some point, where I have no idea how to capture it from a livebook instance (easy in a phx app). This is a reference lib in JS ( https://jsforce.github.io/ https://jsforce.github.io/ ) and there seems to be no maintained alternative on hex.pm unfortunately. So, from scratch it seems, somehow. Additional insight: many big companies do use salesforce, and its internal tooling to produce reports/insights is rather limited, but there is a SQL-like language to do complicated stuff, but there is no way to execute a handwritten query in SF itself, except via API calls from outside. This... would be a perfect fit fro livebook! query SF + other databases to generate a report ad-hoc thats not easily possible right now without adding some heavyweight data warehouse connection!
- josevalim 3y ago
  I wonder if we could proxy OAuth flows to notebooks. For example, a notebook could initiate an OAuth2 flow, Livebook handles it, and once it gets back, we notify the notebook which may approve or deny the request. The biggest concern though is that we need to have a static callback URL, so you would need to run Livebook internally at a fixed address? If this is something you would like to work on, please reach out, I think it could open up interesting possibilities!
  - anonyfox 3y ago
    currently starting to run stuff on fly.io, so the notebooks are public (albeit password protected) - should work this way!
  - anonyfox 3y ago
    update: this specific issue is something I could work around differently: defining a user that has its own credentials within SF who can be used in the auth flow did the trick without any redirect needs! See: https://gist.github.com/Anonyfox/3f36c26fb00a9bc4067d6dc9c9a87137 https://gist.github.com/Anonyfox/3f36c26fb00a9bc4067d6dc9c9a... I sound totally dumb now to bitch about it, but glad I could solve it in like 1 hour in a sufficient way
Dowwie 3y ago
The OAuth2 authorization code workflow involves a redirect step.

I slightly complain a single time for the last few years, and jose directly chimes in with kind words immediately. You rock, honestly! But on the topic: I think its a simple problem ultimately, the SF Api (https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm https://developer.salesforce.com/docs/atlas.en-us.api_rest.m...) needs OAuth, which needs a redirect at some point, where I have no idea how to capture it from a livebook instance (easy in a phx app). This is a reference lib in JS ( https://jsforce.github.io/ https://jsforce.github.io/ ) and there seems to be no maintained alternative on hex.pm unfortunately. So, from scratch it seems, somehow. Additional insight: many big companies do use salesforce, and its internal tooling to produce reports/insights is rather limited, but there is a SQL-like language to do complicated stuff, but there is no way to execute a handwritten query in SF itself, except via API calls from outside. This... would be a perfect fit fro livebook! query SF + other databases to generate a report ad-hoc thats not easily possible right now without adding some heavyweight data warehouse connection!

josevalim 3y ago
I wonder if we could proxy OAuth flows to notebooks. For example, a notebook could initiate an OAuth2 flow, Livebook handles it, and once it gets back, we notify the notebook which may approve or deny the request. The biggest concern though is that we need to have a static callback URL, so you would need to run Livebook internally at a fixed address? If this is something you would like to work on, please reach out, I think it could open up interesting possibilities!
- anonyfox 3y ago
  currently starting to run stuff on fly.io, so the notebooks are public (albeit password protected) - should work this way!
- anonyfox 3y ago
  update: this specific issue is something I could work around differently: defining a user that has its own credentials within SF who can be used in the auth flow did the trick without any redirect needs! See: https://gist.github.com/Anonyfox/3f36c26fb00a9bc4067d6dc9c9a87137 https://gist.github.com/Anonyfox/3f36c26fb00a9bc4067d6dc9c9a... I sound totally dumb now to bitch about it, but glad I could solve it in like 1 hour in a sufficient way

Dowwie 3y ago

The OAuth2 authorization code workflow involves a redirect step.