Permalink
Browse files

Update docs to indicate Twitter requires a setting for authenticate t…

…o behave correctly (i.e. not authorise app each login).
  • Loading branch information...
brightchimp committed Apr 11, 2013
1 parent ea85f83 commit 5780f163a1e87e019d4cfd4bd215adac14c7cd54
Showing with 1 addition and 1 deletion.
  1. +1 −1 README.md
View
@@ -42,7 +42,7 @@ The options are:
* **x_auth_access_type** - This option (described [here](https://dev.twitter.com/docs/api/1/post/oauth/request_token)) lets you request the level of access that your app will have to the Twitter account in question. *Example:* `http://yoursite.com/auth/twitter?x_auth_access_type=read`
-* **use_authorize** - There are actually two URLs you can use against the Twitter API. As mentioned, the default is `https://api.twitter.com/oauth/authenticate`, but you also have `https://api.twitter.com/oauth/authorize`. Passing this option as `true` will use the second URL rather than the first. What's the difference? As described [here](https://dev.twitter.com/docs/api/1/get/oauth/authenticate), with `authenticate`, if your user has already granted permission to your application, Twitter will redirect straight back to your application, whereas `authorize` forces the user to go through the "grant permission" screen again. For certain use cases this may be necessary. *Example:* `http://yoursite.com/auth/twitter?use_authorize=true`
+* **use_authorize** - There are actually two URLs you can use against the Twitter API. As mentioned, the default is `https://api.twitter.com/oauth/authenticate`, but you also have `https://api.twitter.com/oauth/authorize`. Passing this option as `true` will use the second URL rather than the first. What's the difference? As described [here](https://dev.twitter.com/docs/api/1/get/oauth/authenticate), with `authenticate`, if your user has already granted permission to your application, Twitter will redirect straight back to your application, whereas `authorize` forces the user to go through the "grant permission" screen again. For certain use cases this may be necessary. *Example:* `http://yoursite.com/auth/twitter?use_authorize=true`. *Note:* You must have `Allow login with Twitter` checked in your application's settings on [![Twitter](https://dev.twitter.com)] - without it your user will be asked to authorize your each time they log in application - this is a recent change of behaviour for Twitter.
## Watch the RailsCast

0 comments on commit 5780f16

Please sign in to comment.