Skip to content
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

unable to complete the alexa-auth -c config.json #22

Open
Jerry54321 opened this issue Apr 19, 2018 · 6 comments
Open

unable to complete the alexa-auth -c config.json #22

Jerry54321 opened this issue Apr 19, 2018 · 6 comments

Comments

@Jerry54321
Copy link

  • Python Alexa Voice Service version:
  • Python version:
  • Operating System:

I want to "Change Alexa Voice Service client id and product id" to my account.

alexa-auth -c config.json

always fail in connect 192.168.100.1:3000

400 bad request
"The redirect URI you provided has not been whitelisted for your application. Please add your redirect URI in the 'Allowed Return URLs' section under 'Web Settings' for your Security Profile on Amazon Development Portal"

The alexa-auth with on board key login fine.

I have tried many ip address in the 'Allowed Return URLs' and 'Allowed Origins' but still fail with same error above.

I wondering for respeaker what should put on the URLs.
Please advise.

Allowed Origins:
http://localhost:3000/
https://192.168.23.77/
https://localhost:3000/
https://192.168.100.1:3000/
https://192.168.23.77:3000/
https://192.168.23.59:3000/
https://192.168.23.59/
https://192.168.100.1
https://202.131.71.226:3000
https://192.168.23.1:3000/
https://192.168.23.1
https://192.168.100.213
https://192.168.100.213:3000
https://202.131.71.226

Allowed Return URLs
https://192.168.23.77/authresponse
http://localhost:3000/authresponse
https://localhost:3000/authresponse
https://192.168.23.77:3000/authresponse
https://192.168.23.59:3000/authresponse
https://192.168.23.59/authresponse
https://192.168.100.1/authresponse
https://202.131.71.226:3000/authresponse
https://202.131.71.226/authresponse
https://192.168.23.1:3000/authresponse
https://192.168.23.1/authresponse
https://192.168.100.1:3000/authresponse
https://192.168.100.213:3000/authresponse
https://192.168.100.213/authresponse
http://localhost:3000/code
https://localhost:3000/code

Thanks.

@Jerry54321
Copy link
Author

Furthermore, I can not input the http:// in Allowed Origins and Allowed Return URLs
It has to input https:// except the http://localhost

@xiongyihui
Copy link
Contributor

The following is the settings of the respeaker.

image

No idea why you can't add http url. I just tried to add http://192.168.1.1:3000/authresponse to Allowed Return URLs, it works.

Maybe new created produect of AVS requires https.

@susatenk
Copy link

susatenk commented Apr 21, 2018

Also stuck with the same problem. Amazon page says only sandbox environment (localhost) can use HTTP, for all other addresses HTTPS has to be used for allowed return URL. Any advice?

Update: seems this obstacle can be fixed by modifications of auth.py:
a) adding ssl_options to tornado invocation routine
http_server = tornado.httpserver.HTTPServer(application, ssl_options={ "certfile": "/root/certificate.crt", "keyfile": "/root/key.pem", })
b) replacing all "http" by "https" in the file.
Of course certificate and key files have to be generated first.
At least device successfully logged in on AVS . Struggling further.

@crapthings
Copy link

what is this ?

We're sorry!
An error occurred when we tried to process your request. Rest assured, we're already working on the problem and expect to resolve it shortly.

@crapthings
Copy link

wow wrong product id

https://github.com/alexa/alexa-avs-sample-app/issues/5

@theodorehu95
Copy link

I observed that the in the URL, the callback URL becomes "http://1.0.0.127.in-addr.arpa:9000/callback/" instead of http://localhost:9000/callback/, so I added the first one into my security profile, It worked.

Then after finishing the first step, my browser jump to "http://1.0.0.127.in-addr.arpa:9000/callback/?code=ANeLmscGopOgvRciFmBS&scope=alexa%3Aall" which is again not accessable, I manually changed the domain name to localhost again, and I get the refresh token.

I don't know why, but it worked for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants