ForumsDevelopersPlayground:The 3rd party app has not identified itself correctly


Playground:The 3rd party app has not identified itself correctly
Author Message
MikZ

Posted: Nov 07, 2015
Score: 0 Reference
G'day peeps,

I've been wanting to start a project all year, but I haven't managed to graduate past the playground yet. Here's what I'm doing:

i. Go to https://api.toodledo.com/3/playground.php (while logged into ToodleDo)
ii. Try to complete Step 1, by entering this:
AppId: the one I have under 'Registered Applications' at https://api.toodledo.com/3/account/doc_register.php
State: a reasonably random string, specifically 'blah1234random'
Scope: 'basic tasks notes' (but it doesn't really make a difference)
iii. Click the 'authorise' button
iv. A panel opens on the side, saying '[my app] would like access to the following parts of your Toodledo account: Your account settings • Read your tasks • Read your folders, contexts, goals and locations • Read your notes'—pretty much what I asked for in 'Scope'.

BUT, underneath that, it says 'The 3rd party app or service that sent you here has not identified themselves correctly'. I don't get an authorisation code, so I can't go on to Step 2.

I think thinking I must be missing something obvious, but I can't see what it is. Ideas?
Jake

Toodledo Admin
Posted: Nov 09, 2015
Score: 0 Reference
It sounds like you are not entering the correct value into the"AppID" field. What what you want to put there is whatever is in the "Client ID" column on the register page. I realized while researching this ticket that they should be named the same thing, so I'll get that fixed. If you need more help, please create a support ticket and tell us which AppID you are trying to use.
MikZ

Posted: Nov 11, 2015
Score: 0 Reference
Yep—that's what I'm putting there. I'll open a support ticket. Thanks.
MikZ

Posted: Nov 17, 2015
Score: 0 Reference
The support people got back to me with the solution:

'When you registered your AppID, you did not enter anything into the "Redirect URI" field so we have no way to redirect the user back to your app. You need to put something in this field and save the changes and then it will work.

'If you are building an app, the you can redirect to http://localhost.'

Since I was planning to develop my own desktop app, and not a web app, I didn't think that field would matter. But sure enough, when I filled it with http://localhost, everything started working.
Jake

Toodledo Admin
Posted: Nov 18, 2015
Score: 0 Reference
We will update the error message that is displayed to make this easier for developers to debug.
cb_1374830848

Posted: Feb 09, 2016
Score: 0 Reference
I'm still getting "The 3rd party app or service that sent you here has not identified themselves correctly."

Is there any way I can find out what's missing? I'm trying to access with Google Apps Script
Jake

Toodledo Admin
Posted: Feb 09, 2016
Score: 0 Reference
Have you filled out the redirect url?
mschomburg

Posted: Jul 13, 2016
Score: 0 Reference
Hmmm, experienced the same problem upon my first tries with Toodledo-API V3 and OAuth2.

Seems the redirect URL in the request must exactly match the registered URL.
If a desktop application chooses a free port for receiving the redirect, it's naturally difficult to name that port
upon registration.
On the other hand, it's difficult to ensure a specific port is always free.

For Google's own APIs, it's not needed to register the redirect URL that way.

Technically, I'm using Google's Java oauth-Client (com.google.api.client.auth.oauth2.AuthorizationCodeFlow)
which by defaults generates redirect URL's like http://localhost:51202/Callback with an undetermined port.

(Yes, I can make this port a fixed one, and if that URL matches the registered one, everything is fine with Toodledo.
But maybe it would be good to be able to use something like http://localhost:*/Callback ...?)
Jake

Toodledo Admin
Posted: Jul 13, 2016
Score: 0 Reference
Right now, it isn't possible to pass in a dynamic redirect url. Whatever redirect url you registered with your app will be what is used. We may change this in the future, but I dont have an ETA right now.

Here is a suggestion that hopefully will work. If you embed the webview inside your app, then it should be possible to monitor the url of that webview and detect when it changes and grab the contents of the new URL. This way, it won't matter what port you redirect to, since the page doesn't actually need to load anything, it just needs the URL of the page its attempting to load. Does that make sense?
You cannot reply yet

U Back to topic home

R Post a reply

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