Xibo

Client oAuth is not redirecting to callback url

Asked by Yahya BAYRAMOĞLU

I'm developing a client to use some features of Xibo. But i have a verifing problem. I managed request_token and authorize parts of oAuth methods which are described here: http://wiki.xibo.org.uk/wiki/XiboAPI#XRDS

But after authorizing, i am not getting directed to callback url. So i am unable to receive verifier... How can i get the verifier to get access_token correctly? Do i miss something in api documentation?

Thanks in advance.

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
Alex Harrington
Solved:
Last query:
Last reply:
Revision history for this message
Dan Garner (dangarner) said : 		#1

Have you taken a look at the example client?
http://bazaar.launchpad.net/~xibo-maintainers/xibo/head-15-fix/view/head:/example_oauth/index.php

Revision history for this message
Yahya BAYRAMOĞLU (yahyabayramoglu) said : 		#2

Actually i'm developing on Eclipse, so i checked Java Client example: http://bazaar.launchpad.net/~alexharrington/xibo/jclient-dev/files/head:/client/
But couldn't find where the oAuth connection settings handled. That's why i am having some troubles right now.

Revision history for this message
Yahya BAYRAMOĞLU (yahyabayramoglu) said : 		#3

Is there any particular form of callbackurl that i should've specified while creating application? Because i wrote a placeholder such as "http://example.com" because i'll catch calling url and parse it to have verifier but it calls none. So i can't get verifier?

Revision history for this message
Yahya BAYRAMOĞLU (yahyabayramoglu) said : 		#4

By the way, I would rather not to use oAuth because i don't want my users to have to type their username and passwords, just like other client applications, such as Android. But i couldn't find out how can i connect to server except oAuth. Am i on wrong trace or what?

Revision history for this message
Best Alex Harrington (alexharrington) said : 		#5

OK that's where the confusion is.

oAuth is for the API for modifying layouts, uploading media etc. Basically doing the things you can do via the CMS interface.

If you're looking to write a client app like the official display clients, then all you need to do is consume the XMDS SOAP webservice. All the code for doing that is in the existing clients.

If you're doing this as an open project then feel free to ask questions and we'll help where we can. If it's for something closed or commercial then I'd refer you to the XMDS documentation.

Best wishes

Alex

Revision history for this message
Yahya BAYRAMOĞLU (yahyabayramoglu) said : 		#7

I had totally confused, I'll dig more Java Client.
Thank you for your reply.