REST Resource OAuth Session not redirecting to provider


(Nic Hubbard) #1

I am trying to use the REST Resource OAuth Session asset with Twitter. I have all the required info entered, but when I preview the asset as it says in the manual nothing happens, I just see my page previewed.

 

The asset should be redirecting to Twitter for me to authorize it. Is there a reason this isn't happening? Does this asset need to be under the Web Services Folder or something?


REST Resource OAuth Session not redirecting to Twitter
(Bart Banda) #2

Hey Nic, what version of Matrix are you using? Versions older than 4.10.3 have bugs with the REST Oath that might be causing it.

Otherwise it should work fine. I would also try and apply a blank parse file design (just print body) to your Oath Session asset and then try it if you haven't already. 

And no, it doesn't need to sit under the Web Services folder. 


(Anthony) #3

Hi Nic,

You'll see from my comment on the other related post that I didnt get it working, but it sounds like I did get a bit further than you in that I got the Twitter login appearing and made Twitter generate the necessary key. Two thoughts to share with you... (1) I think its the REST OAuth asset you need to preview, not the Rest Javascript asset that will eventually display the twitter feed - I misunderstood that when I first tried it as its not intuitive! (2) On my page, the Twitter login appeared in a really odd place and was partially obscured by some other elements. I guess its just the way the HTML they generate injects itself into the design. Maybe worth selecting a blank design first?

Anthony


(Nic Hubbard) #4

Hey Nic, what version of Matrix are you using?

 

This is on a 4.14.3 install.


(Nic Hubbard) #5

I think its the REST OAuth asset you need to preview, not the Rest Javascript asset that will eventually display the twitter feed - I misunderstood that when I first tried it as its not intuitive! (2) On my page, the Twitter login appeared in a really odd place and was partially obscured by some other elements. I guess its just the way the HTML they generate injects itself into the design. Maybe worth selecting a blank design first?

Anthony

 

Yeah, I am using and previewing the Rest Resource OAuth Session. It works correctly on one Matrix install of mine, but not another.

 

Even using a blank design file with a body area doesn't work. Just prints nothing.


(Edison Wang) #6

I tested latest version Matrix, it works fine for me. 4.14.3 also sounds quite recent, shouldn't have problems.

 

Make sure you check this obvious option.

Redirect To Authorise = Yes

 

Also, be careful with trailing space when you filling the key and secret.

 

Finally, in your twitter developer setting page.

 

Make sure you set the Access level of the application correctly.

Callback URL has to be set too.


(Nic Hubbard) #7

I tested latest version Matrix, it works fine for me. 4.14.3 also sounds quite recent, shouldn't have problems.

 

Make sure you check this obvious option.

Redirect To Authorise = Yes

 

Also, be careful with trailing space when you filling the key and secret.

 

Finally, in your twitter developer setting page.

 

Make sure you set the Access level of the application correctly.

Callback URL has to be set too.

 

Yeah, still not working no matter what I try. Will have to get my client to show me the error logs.