None of the OAuth methods seem to work
dashrandom opened this issue · 8 comments
I've tried setting up Google OAuth2 and Github OAuth but it seems that Tabby Web is unable to parse the OAuth response properly.
Not sure why this is happening, just for context, I had Tabby running on a reverse proxy (Traefik) and Cloudflare proxying my DNS requests to the server. I would love to disable either of them for testing but OAuth redirect URIs need to be HTTPS enabled and disabling either will impact HTTPS as I'm using an ACME DNS-01 challenge for my SSL certs...
I'm getting this for Github but I triple checked the client ID and secret and I'm sure they are right... I have no idea what is going on.
Did you ever sort this out? I'm having the same issue.
@ency98 unfortunately not :(
If you use a reverse proxy.
Replace your Authorization callback URL to http://yourdomain.com/api/1/auth/social/complete/github/.
Do not fill in https, even if your domain name is https.
You may also need to configure http 302 to jump to https.
Unfortunately not possible if my app is in production status for google oauth... I tried for Github and because my application is hosted only on HTTPS and not HTTP, the callback URI is reflecting as not matching...
so bad.
It may be modify source code to completely solve this problem
This project seems dead. Are there other projects that works well you can suggest?
I setup teleport. It's not the same type of thing but it gets the job done. I also setup a Kasm server and have had some decent success with using their terminal container with a persistent storage. But I have not found a good ssh web client. SSHwifty is also an option but I found it a bit limited for what I needed to do.