Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handle expired tokens #2

Closed
spamguy opened this issue Dec 2, 2016 · 1 comment
Closed

Handle expired tokens #2

spamguy opened this issue Dec 2, 2016 · 1 comment
Assignees
@spamguy

Comments

@spamguy
Copy link
Owner

spamguy commented Dec 2, 2016

There's no way to predict when Diplicity tokens will expire. The best thing to do is detect 401 errors with a body of token timed out as they happen, and immediately log off.
@spamguy spamguy self-assigned this Dec 9, 2016
@spamguy
Copy link
Owner Author

spamguy commented Dec 9, 2016

Fixed locally and on prod.

@spamguy spamguy closed this as completed Dec 9, 2016
@spamguy spamguy assigned spamguy and unassigned spamguy May 19, 2017
spamguy added a commit that referenced this issue May 30, 2017
@spamguy
fix(Protractor): Try #2 at Sauce Labs
0482c9f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spamguy spamguy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@spamguy