alexa-pi/AlexaPi

Fix for 400 Bad Request

Open

#366 opened on Jan 21, 2018

View on GitHub
 (8 comments) (2 reactions) (0 assignees)Python (1,324 stars) (402 forks)batch import
bughelp wanted

Description

Fix for the "400 Bad Request" error message when trying to authenticate using http://localhost:5050. This is happening because Amazon requires SSL which isn't supported with this version of AlexaPi. The alternate installation method (https://github.com/alexa/alexa-avs-sample-app) does however support SSL - if you install this you can find the refresh_token that AlexaPi needs to run.

  1. Follow instructions to install alexa-avs-sample-app (https://github.com/alexa/alexa-avs-sample-app).
  2. After setup is complete open the refresh_tokens file (sudo nano /home/pi/Desktop/alexa-avs-sample-app/samples/companionService/refresh_tokens). You'll see a line that starts with "refresh_token:" The token begins at "Atzr...." (ignore the string of numbers prior to Atzr) and is quite long. To copy it I had to scroll to the right, hit return for new line, repeat repeat repeat until I could see it all on one screen. Paste it into a text editor to get rid of all the line breaks and copy it to your clipboard.
  3. Follow the instructions to install AlexaPi. At the end it will prompt you to go to http://localhost:5050, don't bother, it won't work, just close the installer with control c.
  4. Insert the refresh_token into the configuration file for AlexaPi (sudo nano /etc/opt/AlexaPi/config.yaml). Should look something like this: refresh_token: "Atzr | amillionmoreletters"
  5. Start the service with "sudo systemctl start AlexaPi.service"

Contributor guide

Tech stack
pythonshell
Domain
backendauthentication
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic command line experience
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the authentication implementation in AlexaPi, specifically how the refresh token is obtained and used. The issue indicates that Amazon requires SSL, so consider adding HTTPS support to the local server or documenting the workaround involving the Amazon AVS sample app. Relevant files likely include `auth.py` or similar in the AlexaPi codebase. The issue's comments may contain additional context about the SSL requirement.