1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
Twitter
=======
Twitter offers per application keys named ``Consumer Key`` and ``Consumer Secret``.
To enable Twitter these two keys are needed. Further documentation at
`Twitter development resources`_:
- Register a new application at `Twitter App Creation`_,
- Check the **Allow this application to be used to Sign in with Twitter**
checkbox. If you don't check this box, Twitter will force your user to login
every time.
- Fill **Consumer Key** and **Consumer Secret** values::
SOCIAL_AUTH_TWITTER_KEY = ''
SOCIAL_AUTH_TWITTER_SECRET = ''
- You need to specify an URL callback or the application will be marked as
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
|
