cakebake / node-red-contrib-alexa-remote-cakebaked

Forked for me and the community to keep dependencies up to date :)
MIT License
42 stars 6 forks source link

How to make an old cookie-file not valid any more? #45

Open zeldalegends opened 2 years ago

zeldalegends commented 2 years ago

Hi,

I have fetched a token and saved it in the cookie-file correctly in a past project. Now I have created another project with another Node-RED installation, and I would like to authorize ONLY this new Node-RED installation with the same Alexa Echo Dot. At the same time, I would like toget rid of the former Node-RED installation an prevent it to access Alexa Echo Dot for security. So, I fetched a new token and saved into a new cookie-file for the new Node-RED installation, but unfortunately the old one is still working in the previous project... I would like to avoid that the old Node-RED can access Alexa with the old cookie file.

How can I do?

Thanks

MonkeyBusiness1 commented 2 years ago

I would think it would be as easy as deleting the cookie file and disabling any refresh routine so the next time it authorization is needed it will fail and not be able to get a refreshed cookie file. Just in case you might want to remove the login credentials from your regresh routing as well.