Skip to content
This repository has been archived by the owner on Feb 25, 2020. It is now read-only.

Access tokens expiring caught me completely off guard #33

Open
streblo opened this issue Dec 15, 2014 · 2 comments
Open

Access tokens expiring caught me completely off guard #33

streblo opened this issue Dec 15, 2014 · 2 comments

Comments

@streblo
Copy link

streblo commented Dec 15, 2014

Please let me know if I should move this issue to a better spot.

My access token expired and I had no idea that this happens. I understand it is probably for good reason (security, etc.), but I think the user should be better informed by any of the following ways:

  1. Notice of expiration date when creating access tokens ("This token will expire on xxxx-xx-xx.")
  2. Email reminding 1 week before token expiration
  3. Change the error message from "Authorization is required to perform that action." to "Expired access token."

Thank you for truly amazing platform -- can't wait to see where this goes!

@zsup
Copy link
Member

zsup commented Dec 15, 2014

good feedback! this is an issue that's come up before, but I'll leave this open so we remember. agreed that we should notify people about expiring tokens, and these are great suggestions.

@streblo
Copy link
Author

streblo commented Dec 16, 2014

/me dons his red face.

In my case, it was actually not Spark that lost authorization but rather the data logging platform (Google Sheets) which lost authorization. Today was a wonderfully serendipitous day if my error helped register a legit issue for Spark.

lbt pushed a commit to lbt/spark-server that referenced this issue Feb 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants