Jump to content

Archived

This topic is now archived and is closed to further replies.

tipudj

oauth requests are failing

Recommended Posts

At first I was using the evernote3 python client and was requesting a token using,

client.get_request_token('http://localhost:5000')

However I kept getting this response:

<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=9,chrome=1" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
<link rel="Shortcut Icon" href="/favicon.ico" type="image/x-icon" />
<link rel="stylesheet" href="/redesign/global/css/reset.css" />

<link rel="stylesheet" href="/redesign/global/css/fonts.css" media="all" />

<link rel="stylesheet" href="/redesign/global/css/header.css" />
<link rel="stylesheet" href="/redesign/global/css/layout.css" />

<title>Evernote Error</title>
</head>
<body>
  <div class="header">
    <div class="header-inner">
      <a href="https://evernote.com/" class="evernote-logo">Evernote</a></div>
  </div>
  <div id="container-boundingbox" class="wrapper">
    <div id="container" class="wrapper">
      <div class="main">
        <div class="page-header">
          <h1>
            Oops, we encountered an error.</h1>
        </div>
        <div>
          <p>
            Sorry, we've encountered an unexpected error.</p>
        </div>
        <div class="clear"></div>
      </div>
    </div>
    <div class="footer wrapper">
      <a href="https://evernote.com/tos/" class="footer-entry">Terms of Service</a><a href="https://evernote.com/privacy/" class="footer-entry">Privacy Policy</a><span class="footer-entry last">Copyright 2016 Evernote Corporation. All rights reserved.</span>
    </div>
  </div>
</body>
</html>

So I started using curl to see what might be going on and the sandbox is giving me the same response using the sample,

curl "https://sandbox.evernote.com/oauth?oauth_callback=http://www.foo.com&oauth_consumer_key=sample-api-key-4121&oauth_nonce=3166905818410889691&oauth_signature=T0+xCYjTiyz7GZiElg1uQaHGQ6I=&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1429565574&oauth_version=1.0

I'm getting the same result. Any ideas why this is happening?


 

 

 

 

 

Share this post


Link to post

×
×
  • Create New...