You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something Ive done is stored my tokens in a db.
I then retrieve the latest token by its expiry date.
if the expiry date has lapsed or is close to todays date I then generate a new one and save it in the db
Alright. Do you think it's worth it to write such a function or should we just leave it up to the user to set the auth, load a new token, and then set the new token? (If they started without a token for example)?
I think this should be a connector clash and it should be stateless.
If we add dbs to it it will just raise the requirements needed to get connected to a spark core
Oh, I do agree with that. I was simply thinking about a function to make the whole get-and-use-access-token-for-this-session-only process easier. Perhaps in a separate branch.
Activity
devinpearson commentedon Mar 16, 2015
Something Ive done is stored my tokens in a db.
I then retrieve the latest token by its expiry date.
if the expiry date has lapsed or is close to todays date I then generate a new one and save it in the db
harrisonhjones commentedon Mar 16, 2015
Alright. Do you think it's worth it to write such a function or should we just leave it up to the user to set the auth, load a new token, and then set the new token? (If they started without a token for example)?
devinpearson commentedon Mar 17, 2015
i recon we leave that for the dashboard.
I think this should be a connector clash and it should be stateless.
If we add dbs to it it will just raise the requirements needed to get connected to a spark core
harrisonhjones commentedon Mar 17, 2015
Oh, I do agree with that. I was simply thinking about a function to make the whole get-and-use-access-token-for-this-session-only process easier. Perhaps in a separate branch.