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
I maintain the omniauth-heroku strategy, and some of our users keep running into issues when they don't provide a proper client id and secret, which can be hard to debug because the oauth strategy will just attempt to redirect anyways.
Is there a use case for omniauth-oauth2 in which you don't provide a client id and secret? If not I can definitely open a pull, any feedback on how that was handled is welcome.
Thanks,
The text was updated successfully, but these errors were encountered:
Hey folks!
I maintain the omniauth-heroku strategy, and some of our users keep running into issues when they don't provide a proper client id and secret, which can be hard to debug because the oauth strategy will just attempt to redirect anyways.
I've added a validation to our strategy, but now wondering if this shouldn't be validated here.
Is there a use case for omniauth-oauth2 in which you don't provide a client id and secret? If not I can definitely open a pull, any feedback on how that was handled is welcome.
Thanks,
The text was updated successfully, but these errors were encountered: