-
Notifications
You must be signed in to change notification settings - Fork 337
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
How to handle non LWA authentication #8
Comments
Here's a blog, as a guide for LwA implementation - https://developer.amazon.com/blogs/post/Tx3CX1ETRZZ2NPC/Alexa-Account-Linking-5-Steps-to-Seamlessly-Link-Your-Alexa-Skill-with-Login-wit |
@modescode I don't want to use LWA |
@albinantony2904 setting up the OAuth provider is not something we can provide documentation for as this will vary greatly depending on the web platform you are using. However we do have some documentation which can help you with configuration based on what Alexa is expecting: |
To add to @modescode and @briankel's comments, we expect smart home skill authorization to be based on the OAuth 2 spec, so if you do not want to use LWA, then you can use any other OAuth 2 compliant provider. Resolving this issue, please re-open if needed, thanks! |
I am planning to direct the user to a login page that I provide in companion app when the user tries to enable a smart home skill.So how can I handle such kind of authentication.? Is there any tutorial available that does not involve LWA authentication.?
The text was updated successfully, but these errors were encountered: