-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Store the accessToken expiration #525
Comments
I'll answer your question from the other thread here. I am using the username/password for imap. I don't need an oauth token for that. I'm using node-imap. Here is the code for the connection.
Nothing fancy. I don't know how to access gmail using anything that would require oauth. |
I see - I don't have the user's password - frankly I don't think any sane user would give out the password to the emails to be stored elsewhere :-) I just add the GMail scope when users sign up to my Meteor app and then use the OAuth data to access GMail. |
Cool. I'll have to look into how to do that. Thanks. |
Sure - it works with |
It's quicker to put in a pull request. Should not be difficult to add. |
I would happily review a pull request implementing this but I don't think the meteor core team is going to work on this for now. |
@avital Is that what you've been looking for? |
@AVGP nice work! |
Update eslint to the latest version 🚀
Link to http://react-components.com/ displays 'Service Unavailable'.
Use case:
I want to use the
accessToken
to access a GMail account with it. Therefore I need to know the time when the accessToken expires, hence I need the lifetime (or more specifically now()+liefetime) that comes back with theaccessToken
to be stored, so I can just use theaccessToken
if it hasn't expired and only refresh it using therefreshToken
if its expired before accessing GMail via IMAP.Feature request: Store the timestamp of the
accessToken
expiration (now()+lifetime) within the user record, when updating theaccessToken
.Related discussions: #495, #464, #522
The text was updated successfully, but these errors were encountered: