You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My organization provides OAuth for a few different services and we'd like to use it for Loomio, too. I see that you support Facebook, Twitter, Google, and Slack from within the .env file, but I'd like to use a different OAuth service tied to a login.example.com that we host.
For most apps that don't support custom OAuth I use Vouch, which acts as a wrapper to the app but also requires that I'm able to edit the nginx config on the server that the application is hosted. I could edit files directly in the nginx-proxy docker container but that seems a little brittle and not best practice, right?
How do self-hosting orgs that use their own OAuth manage this?
The text was updated successfully, but these errors were encountered:
Hi, it should be possible to get loomio to support a custom oauth, but I'm not sure how right now. If you need we could look into adding this as some sponsored development.
We do support SAML really well though, if that's possible with your setup?
You can edit the nginx.conf file within the loomio-deploy directory you have. It's currently just one line.
(Thanks for your help earlier today.)
My organization provides OAuth for a few different services and we'd like to use it for Loomio, too. I see that you support Facebook, Twitter, Google, and Slack from within the
.env
file, but I'd like to use a different OAuth service tied to alogin.example.com
that we host.For most apps that don't support custom OAuth I use Vouch, which acts as a wrapper to the app but also requires that I'm able to edit the nginx config on the server that the application is hosted. I could edit files directly in the
nginx-proxy
docker container but that seems a little brittle and not best practice, right?How do self-hosting orgs that use their own OAuth manage this?
The text was updated successfully, but these errors were encountered: