Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Create option to disable authentication entirely
See original GitHub issueWait, hear me out!
In March of 2019, Google+ Oauth will be deprecated, and thus will no longer work with SQLpad, so I’ve been looking at different ways to handle SQLpad authentication. One of the things my institution already uses for authentication is oauth2_proxy (with regular Google Oauth2, which is apparently different from Google+ Oauth) behind an Nginx auth_request. The oauth2_proxy / auth_request part of this seems to work just fine with SQLpad, however, it doesn’t look like there is a way to disable the built-in authentication, so once a user authenticates with oauth2_proxy, they still hit the Google+ oauth or the userpass auth page. Is there something I’m missing, or is this a feature for which PRs might be accepted?
Issue Analytics
- State:
- Created 5 years ago
- Comments:9
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is in 4.2 release, just now tagged. https://rickbergfalk.github.io/sqlpad/#/authentication?id=no-authentication
Auth proxy is also an option https://rickbergfalk.github.io/sqlpad/#/authentication?id=auth-proxy
Thanks for your work on this @bruth @hessam61!
I really appreciate the guidance on getting started! We will take a pass at it to get it started and ask follow-up questions as needed. Thanks!