Hi,
Amazon is continuesly approving the authentication methods, so the Email/pass is already and proxy/cookie will be in the future obsolet.
I've invested some Time to enable OAuth in node-red-contrib-alexa-remote2-applestrudel - trying to compense my knowledge lecks in javascript developpment with KI help. Result was the first PR in GitHub, which was unfuturnatelly not free of bugs (PR #244).
Thanks great work of @gtalusan is the OAuth implementation working - (Rel. 5.0.58 GitHub - bbindreiter/node-red-contrib-alexa-remote2-applestrudel: Node-Red Nodes for interacting with Alexa · GitHub).
But I'm not quite happy with my PR and the (now working) result. After more analysis of the coding I've found out that the better way to implement a new (OAuth) authorisation method is primary to create a new config-node - is what we see creating a new every alexa-remote2-applestrudel node under Account:
My idea is to create a new Account type 'OAuth' which afford changes in alexa-remote-account.js and its UI alexa-remote-account.html (see fork alexa-remote2-applestrudel (TokenAuth))
The processing of alexaInit() is splittet there depending of using authentication method to initDefault(), initToken() and initOAuth(). The first inludes all authentication methods till Rel. 5.0.55 (proxy, cookie, Email/Password).
The UI of config-was changed there accordingly:
Now is for me following to resolve: How should the authentication method OAuth with a new config-node work?
The actuall working authentication method is 'cookie', which uses internal 'proxy' for the first login and then 'cookie' and/or 'token' saved in node-red locally (Field Path which contains path incl. filename(!))
The OAuth implementation of '@gtalusan' seems to be included in 'cookie' method and extends it with refreshToken proceeding (incl. local saving). My solution could give the possibility - via Account authentication method - to choose which one method is to be used.
Unfortunately I'm not be able yet to splitt the actual mixed cookie/oauth solution into two separately usable cookie and OAuth methods, so my above Fork can be used as Template only (The Token and OAuth there are still buggy).
Maybe somebody can use my post as inspiration to get this solution working?
By the way I'm not sure how the Amazon OAuth authentication method ist really working. From my expieriences in B2B there were used encrypted user/login account to get connect, after succesful Handshake the Token and refreshToken were requested and received. Next the refreshToken was validated and refreshed if needed (short before validity time was ending).
Makes it Amazon this way?
