-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AccessToken expiry... #7
Comments
You're right. I would rather keep expires_in as Devise.timeout_in. Do send me a pull request. |
Please find the referenced pull to set the AccessGrant life. I'm suspecting there is still more work to do regarding renewing expiring tokens - there is currently no handling of refreshes - is that right? From what I see, the oauth2 client will call the auth_controller access_token with |
Yup - I dont think I handle a token refresh. When I set this up the first time (earlier version of oauth), refresh_token I'll fix that.http://www.joshsoftware.com Josh Software Pvt. Ltd. On Tue, Feb 7, 2012 at 11:05 AM, Gavin Brock <
|
In the AuthController, when a client is granted an access token (an AccessGrant instance) and
start_expiry_period!
is called, an expiry of two days is stored in the database. However the AuthController then goes on to send anexpires_in
ofDevise.timeout_in
to the client, which in my case seems to be 30 minutes.Unless I'm mistaken (which is quite possible!), shouldn't the
expires_in
be read from the AccessGrant, or both of theses read from Devise.timeout_in?If you have a preference for which, I'll put in a pull request.
Regards,
Gavin
The text was updated successfully, but these errors were encountered: