4 ms·
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 notif
by 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 agocurrently starting to run stuff on fly.io, so the notebooks are public (albeit password protected) - should work this way!
- anonyfox 3y agoupdate: 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