Authorization URL

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Justin Greer

    (@justingreerbbi)

    Hi,

    The authorization URL is https://mysite/?oauth=authorize. This will ask the user to login if they are not. Once the user is logged in, they will be redirected back to your Alexa application.

    From there, the user should then be redirected to https://mysite/?oauth=token to recieve an access token.

    Of course this is a high level explanation. You can visit https://tools.ietf.org/html/rfc6749#page-23 to get a better idea what really is happening.

    Thanks

    Thread Starter ddarby14

    (@ddarby14)

    Excellent, thanks for the quick response and clarification on URI. That works!

    One thing we had to do, Alexa gives TWO possible URIs as shown in the screenshot above. I first received an error using the https://mysite/?oauth=authorize, then had to change in the plugin, the Client URI. Then it worked.

    If Alexa goes back and forth between two possible URIs, how do we adapt for that?

    Plugin Author Justin Greer

    (@justingreerbbi)

    Try not adding any value to the redirect URI for the client. It has been a while since I have worked on the area of the plugin but I recall it not needing a value.

    Try not value and see what happens. Please update.

    Plugin Author Justin Greer

    (@justingreerbbi)

    Try not adding any value to the redirect URI for the client. It has been a while since I have worked on the area of the plugin but I recall it not needing a value.

    Try not value and see what happens. Please update.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Authorization URL’ is closed to new replies.