Permalink
Browse files

Mention how server datetime might cause errors on some backends. Refs #…

  • Loading branch information...
1 parent 0fcbc02 commit 6cd35a97d911bddd2d852165ac1c3041ac73e82a @omab committed Nov 15, 2012
Showing with 16 additions and 0 deletions.
  1. +6 −0 doc/backends/twitter.rst
  2. +10 −0 doc/miscellaneous.rst
View
6 doc/backends/twitter.rst
@@ -18,5 +18,11 @@ To enable Twitter these two keys are needed. Further documentation at
Client type instead of the Browser. Almost any dummy value will work if
you plan some test.
+
+Twitter usually fails with a 401 error when trying to call the request-token
+URL, this is usually caused by server datetime errors (check miscellaneous
+section). Installing ``ntp`` and syncing the server date with some pool does
+the trick.
+
.. _Twitter development resources: http://dev.twitter.com/pages/auth
.. _Twitter App Creation: http://twitter.com/apps/new
View
10 doc/miscellaneous.rst
@@ -48,6 +48,16 @@ Facebook backend. The bug report `#315`_ explains it a bit more and shows
a workaround fit avoid it.
+Server date time
+----------------
+
+Bad date in the server might cause errors in the auth process on some services
+like Twitter (probably all OAuth1.0 since timestamp is passed in the parameters
+to request a token).
+
+This issue is usually solved by installing ``ntp`` in the server (which is
+a good practice to have too), and syncing the time with some ntp pool service.
+
.. _South: http://south.aeracode.org/
.. _django-social-auth: https://github.com/omab/django-social-auth

0 comments on commit 6cd35a9

Please sign in to comment.