Doesn't seem to handle "realm" properly.

[jt55401]

The method we're calling requires the use of the Oauth realm, and we tried specifying that in the request_data.data map we sent do the oauth.authorize method. This "almost worked", but not quite.

Issues:

1. The realm was included in the string to sign, but that should not be so.
2. The realm was properly included in the OAuth header string, but it was last (per alphabetical order) but realm is required to be first in the header.

We worked around for now by NOT specifying the realm in the data, and instead, manually adding it before use...

var request_data = {    
    url: 'http://www.example.com',
    method: 'GET'
};

// generate the auth header WITHOUT any realm.
var headers = oauth.toHeader(oauth.authorize(request_data, token));
// manually add the realm after the fact:
headers.Authorization = headers.Authorization.replace("OAuth ", 'OAuth realm="12345",');

request({    
    url: request_data.url,
    method: request_data.method,
    headers: headers
}, function(error, response, body) {    
    console.log(body);
});

[ddo]

working on it soon

[ddo]

please checkout the newest code and test with your oauth service. the new options is realm, ex:

var oauth = new OAuth({
    consumer: {
        key: "batch-dbc2cd8c-6ca8-463b-96e2-6d8683eac6fd",
        secret: "4S4Rvm25CJZWv7HBg5HOhhlRTBSZ7npl"
    },
    realm: "https://ddo.me/",
    signature_method: 'HMAC-SHA1',
    hash_function: hash_function_SHA1
});

i will public on npm after your tests. ty

[jt55401]

Will do later today, thanks!

[RobGriggs]

Hi there @ddo,

I've been working @jt55401. He figured out the workaround when I was unable implement the library using a realm. I pulled the latest code into the my project and reconfigured my connection script to follow the format that you outlined above.

Connection was successful using the new realm option!

Thanks all.

[ddo]

does your realm contain any non alphabet characters such as /, :

[jt55401]

in our case, no.

[ddo]

so everything ok?

[jt55401]

Yes, works great now!

[ddo]

ty

https://github.com/ddo/oauth-1.0a/releases/tag/2.2.0