search

ndrong / zivver-thunderbird

Zivver for Thunderbird automatically decrypts Zivver messages in your inbox using the Zivver API.
https://addons.thunderbird.net/thunderbird/addon/zivver-thunderbird/
MIT License
3 stars 0 forks source link

Unable to copy refresh token #1

Open Intratex opened 2 years ago

Intratex commented 2 years ago

It doesn't seem possible to paste the refresh token in the [Refresh token] field. Is this correct or have I missed something.

Furthermore, I did find the temporary access tokens via the Developer Tools (GETwss://app.zivver.com/api/ws/Z1.1.2......), but the refresh token remains untraceable.

And finally, does it only work with Thunderbird version 78.0, or also with the most recent (91.10.0 - 64 bits) ?

ScvWebFire commented 2 years ago

Same questions.

ndrong commented 2 years ago

Thank you both for reporting this issue! Also, apologies for the late response on my end. I'm quite busy at the moment but will try to investigate this issue later this week. I just tested this on macOS running the latest stable release of Thunderbird and copy-pasting appears to work just fine. May I ask on which platform you are running Thunderbird (Windows/Linux/macOS)?

djoris commented 9 months ago

Old issue, but since it's still open: I have the extension installed seemingly successfully on Thunderbird 11.6.1 as of now.

djoris commented 9 months ago

As for the issue with the refresh token: I was perhaps confused by the instructions and screenshot in README. I also initially thought the extension wasn't working, but that was because I was testing old messages that I couldn't open in the Zivver Web App either.

a few clarifications about my path:

In the README it mentions under 5: " 'Email address' field", in the preferences it is "Username". I can not right-click either field to paste, but I can use my keyboard shortcut to paste. I can also just type. Pressing the 'Save' button yields no visual confirmation of any kind.

It seems to indicate I have to look at the request parameters. In my first POST to 'login' the refresh_token and username were not requested, but were the responses. In later POSTs to 'login' these parameters were requested.

If appreciated, I might be able to submit a merge request for the README from my lessons. if #2 would be implemented, that would be even better :)