Short version: I would like additional control over the endpoint path.
Long version:
Currently, I have my own implementation of Alexa using very basic blocks in Node-JS. While it works, I would like to take advantage of the features and ease you have in your nodes (such as complete message verification built-in).
For security reasons, I do not allow outside access to http://myinternalserver:1883 root. Instead, I use a nginx proxy (which handles SSL termination) that allows external access to just http://myinternalserver:1883/alexa/*. This way, those outside my network are limited to what is on my /alexa path and therefore cannot easily access everything else on my server (such as the node-red admin page). While I could manually add each Alexa skill endpoint to my proxy, I would prefer to stick with an open endpoint if possible!
At a minimum, I would like to define a root path to base everything off of. For example, use _/mypath//alexa where "mypath" is a configuration option in settings.js. If you really wanted to raise the bar, allow for complete control of the path on the skill configuration page instead. You could then just suggest the current //alexa_ path as a default.
TinajaLabs
commented
7 years ago
Short version: I would like additional control over the endpoint path.
Long version:
Currently, I have my own implementation of Alexa using very basic blocks in Node-JS. While it works, I would like to take advantage of the features and ease you have in your nodes (such as complete message verification built-in).
For security reasons, I do not allow outside access to http://myinternalserver:1883 root. Instead, I use a nginx proxy (which handles SSL termination) that allows external access to just http://myinternalserver:1883/alexa/*. This way, those outside my network are limited to what is on my /alexa path and therefore cannot easily access everything else on my server (such as the node-red admin page). While I could manually add each Alexa skill endpoint to my proxy, I would prefer to stick with an open endpoint if possible!
At a minimum, I would like to define a root path to base everything off of. For example, use _/mypath//alexa where "mypath" is a configuration option in settings.js. If you really wanted to raise the bar, allow for complete control of the path on the skill configuration page instead. You could then just suggest the current //alexa_ path as a default.
Thanks!