-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
invalid_request: Internal server error #3
Comments
I am encountering the same issues now. |
Are you using a https redirect url? It's possible to end up with a non-ssl redirect url in Mashery which isn't allowed and can result in this error. |
I am using an http URL.
|
Battle.net oauth requires an https redirect url, switch that up and you should be good. |
Pushed to Heroku to test via http, still getting similar error:
|
I just checked out the master branch of this project. Setup stunnel to setup a https proxy (my method of running local ssl). I then made sure that my test key had the correct redirect url setup on dev.battle.net and put the client id and secret into my environment as "BNET_ID" and "BNET_SECRET" (where the example sinatra app checks for it). After doing that the app is working fine and logging me in and returning my actual battle tag. Could your application on dev.battle.net not have the correct redirect_url for the new heroku app on it? |
I create a app: Put in name 'Armory Plus (Dev)' Set my env vars for the specified key and secret. I visit the auth URL, and it redirects me to |
Thanks for replies. I'll try to use HTTPS and let you know the results. |
@kelsin I figured it out, there is an issue in newer versions of |
That makes sense! I was using my Gemfile.lock from a long time ago, I will look at fixing what ever the problem is there. Thanks! |
Awesome, glad we figured it out, can continue building my app now! Thanks for the help. |
Hello! |
|
To get around this bug: Blizzard/omniauth-bnet#3
Hello!
I try use Sinatra example of omniauth-bnet, and get this error:
Authentication Failed:
message:invalid_request
{"message"=>"invalid_request", "origin"=>"http://mysite.com/", "strategy"=>"bnet"}
I test this multiple times, on different versions of ruby and gems, but still get "Internal server error"
which no explanation.
Anyone can help me? :)
The text was updated successfully, but these errors were encountered: