Been bedeviled for a while on 401 Unauthorized. Where is the documentation and what are the proper _path variables? (request_token_path, authorize_path, access_token_path)
401 appears to be an extremely frequent problem. Are there any decent diagnostic tools available? If not, why not, then?
Also, in the documentation, I only see 'PLAINTEXT' signature_method. I can use the default 'HMAC-SHA1', right?
@consumer = OAuth::Consumer.new('cce59e8e-05ed-4e20-914a-0a9781e8f834',
'15xxxxc6-7xx5-4xxa-8xxe-85xxxxxxxx35', # consumer_secret
:site => 'https://external.ningapis.com',
:scheme => :header, # default - or :body
:http_method => :post, # default - or :get
:signature_method => 'HMAC-SHA1',
:request_token_path => '/xn/rest/eldorado2/1.0/Token?xn_pretty=true',
:authorize_path => '/xn/rest/eldorado2/1.0/authorize',
:access_token_path => '/xn/rest/eldorado2/1.0/access_token',
:timestamp => Time.now.utc.to_i,
:nonce => Time.now.utc.to_i # arbitrary - use only once
@request_token = @consumer.get_request_token(:oauth_callback => 'http://ee3.rebates4sure.com/oauth/ning/callback')
401 unauthorized at the @request_token above. (BTW, :authorize_path and :access_token_path are just my guess). Can't get past this last statement. Even though adjusted version (key / secret / ...) works with twitter, linkedin, yahoo, tumblr,
Hey, John. Sorry, but I am confounded by your post. It sounds like you may have a deep technical question that I may not be able to answer. Have you tried reaching out on our Developer's community?
Apologies, Eric. Having trouble getting an account / email address squared away on the Developer's side of the house.
Can you have someone there setup a dummy account or otherwise email me so I can go to where I'm supposed to be?
Sorry for any delays. I will check into this.