Could xeroizer 2.15.5 work with oauth 0.4.7 ? about xeroizer

[waynerobinson]

It was downgraded to resolve a specific PUT/POST issue in Xero I believe.
Xero was supporting non-standard syntax and was broken with the newer
version of the gem.

I'm not sure if Xero has fixed this or not.

On 06/08/2013, at 2:50 AM, Zack Xu [email protected] wrote:

Hi.

I updated xeroizer to the latest version 2.15.5, however, I noticed this
depends on oauth 0.4.5.

So in our gem bundle, oauth was downgraded from 0.4.7 to 0.4.5 as a result
of the xeroizer update.

Is there any reason for this specific dependency? In other words, can
xeroizer be updated to work with oauth 0.4.7?

Would this oauth downgrade to 0.4.5 have any negative impact? for anyone
who has done this.

Thanks!
Zack

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/95
.

[zackxu1]

Thanks for the comment, Wayne.

[zackxu1]

I contacted Xero support about this, and here's their response (email sent from technical support):

"I had a chat about this with one of the developers and unfortunately he said it is not fixed.
He suggested though that you might want to create a fork for Xeroizer and update it yourself with the latest OAuth gem to see if it will works.
Sorry we can't be much of help at this time."

[toxaq]

This was locked with commit 27c0a48 Shame there's not more info. It simply states

Corrects some issues with signatures being invalid for PUT requests

[waynerobinson]

The issue was specifically with Xero not being able to accept PUT requests
with a more modern syntax offered by later versions of OAuth.

I can't recall the actual error, but there was an issue that, after
consultation with the Xero team with them accepting PUT requests correctly.
Keeping OAuth back resolved this issue. You're welcome to test upgrading
and attempting requests against the API that will use PUT and see if Xero
has resolved these issues.

On Monday, March 17, 2014, Scott [email protected] wrote:

This was locked with commit 27c0a4827c0a483268b1cba3cca7c5c4d826ad474efebebShame there's not more info. It simply states

Corrects some issues with signatures being invalid for PUT requests

Reply to this email directly or view it on GitHubhttps://github.com//issues/95#issuecomment-37783027
.

[toxaq]

Apologies if this came across as a request for work. I was simply trying to add some references to the issue as I was looking in to it and thought it could be useful to others. I'm not currently affected by it but was intrigued by the change. With your extra info I've found the related conversation and commit here (with comments from the Xero team) : oauth-xx/oauth-ruby#34
Thanks for a fantastic gem!

[waynerobinson]

Not a problem. It's possible Xero has fixed this now. At some point the
Xero API needs testing against the newer Gem.

On 17 March 2014 15:21, Scott [email protected] wrote:

Apologies if this came across as a request for work. I was simply trying
to add some references to the issue as I was looking in to it and thought
it could be useful to others. I'm not currently affected by it but was
intrigued by the change. With your extra info I've found the related
conversation and commit here (with comments from the Xero team) :
oauth-xx/oauth-ruby#34 oauth-xx/oauth-ruby#34
Thanks for a fantastic gem!

Reply to this email directly or view it on GitHubhttps://github.com//issues/95#issuecomment-37784181
.

[nathany]

Any progress on getting this updated to use OAuth 0.4.7 or opening an issue in OAuth?
https://github.com/oauth-xx/oauth-ruby

[waynerobinson]

Resolved in #166