{"title":" play! framework 1.2.5\u306eTwitter-OAuth\u30b5\u30f3\u30d7\u30eb\u3067\u30a8\u30e9\u30fc","published":"2013-02-06 00:00:00","url":"https://tmftake.hateblo.jp/entry/20130206/playframework_twitter_oauth_sample_error","blog_url":"https://tmftake.hateblo.jp/","author_name":"tmftake","provider_url":"https://hatena.blog","author_url":"https://blog.hatena.ne.jp/tmftake/","version":"1.0","blog_title":"\u3051\u307f\u304b\u308b\u306f\u3066\u306a","description":"play! framework 1.2.5\u306etwitter-oauth\u30b5\u30f3\u30d7\u30eb\u3092\u52d5\u304b\u3057\u3066\u307f\u305f\u304c\u3001\u4ee5\u4e0b\u306e\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u305f\u3002 Error connecting to twitter: OAuth.Error: NOT_AUTHORIZED - Authorization failed (server replied with a 401). This can happen if the consumer key was not correct or the signatures did not match. \u30a8\u30e9\u30fc\u5185\u5bb9\u3092\u57fa\u306bconsumer key\u3068consumer secret\u3092\u78ba\u8a8d\u3057\u305f\u304c\u3001\u3069\u3061\u2026","image_url":null,"height":"190","width":"100%","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Ftmftake.hateblo.jp%2Fentry%2F20130206%2Fplayframework_twitter_oauth_sample_error\" title=\" play! framework 1.2.5\u306eTwitter-OAuth\u30b5\u30f3\u30d7\u30eb\u3067\u30a8\u30e9\u30fc - \u3051\u307f\u304b\u308b\u306f\u3066\u306a\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","provider_name":"Hatena Blog","categories":["playframework"],"type":"rich"}