Forums > Developers

api usage requires userpassword

Author	Message
HansD	Posted: Dec 12, 2011 Score: 1 The current api (v2) requires the usage of the user password (or just the md5 hash of the password) for signing requests. As I want to some webbased app I'd prefer not to have these in my environment. Instead I would like to see something like oauth where I get a user & app specific token to sign my requests with. To completely redesign the api would be too much, I might have some suggestions/ideas where the impact could be minimised to achieve this.
Jake Toodledo Admin	Posted: Dec 12, 2011 Score: 1 Oauth is a planned upgrade for a future version of the API.
thejspr	Posted: Feb 11, 2012 Score: -1 Oauth definitely sounds like an improvement. Any hint as to when this feature will be available?
Jake Toodledo Admin	Posted: Feb 11, 2012 Score: 1 This is on our to-do list, but it is our policy to not comment on our roadmap or delivery dates for future feature improvements.
Warren	Posted: Mar 27, 2012 Score: 1 Please consider keeping a non-oauth solution available. My workplace completely blocks all social sites and I cannot use oauth based websites as a result.
Jake Toodledo Admin	Posted: Mar 27, 2012 Score: 0 We will, but it will be up to application developers to support both routes.

To participate in these forums, you must be signed in.

Toodledo Forums > Developers