Authorize Issue about milkman HOT 2 CLOSED

I haven't been using the gem myself anymore and I've haven't had a lot of time to fix it either, so this was long overdue, but it's fixed now.

Like @nickaknudson already explained RTM first required the shared_secret, but has correctly changed it to only be used to generate the API signature in the Authorization and Request API calls.

I've updated the gem from v0.0.3 to v0.0.4. This version includes the fix for the shared_secret issue. After that I've release another version (v0.0.5), the latest version, which now uses the V2 API from RTM by default.

from milkman.

I also ran into this problem. The issue is that the RTM API is rejecting the request because the FROB request being generated by Milkman contains both format and shared_secret parameters. The format parameter is not supported by the FROB request. The shared_secret parameter should never be sent to the API and RTM has correctly updated their API to always reject the shared_secret parameter.

I had started a branch to fix these issues, but then switched to using the Rumember gem which appears to be working well. It currently lacks support for API v2 (as do all other ruby RTM APIs that I have found).

Hope this helps someone else.

from milkman.