-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Adds endpoint for non-revocable session token upgrade #2646
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
Conversation
Current coverage is 92.16% (diff: 93.33%)@@ master #2646 diff @@
==========================================
Files 99 99
Lines 12113 12166 +53
Methods 1488 1495 +7
Messages 0 0
Branches 1996 1999 +3
==========================================
+ Hits 11154 11213 +59
+ Misses 959 953 -6
Partials 0 0
|
@flovilmart updated the pull request - view changes |
0138070
to
e855c1a
Compare
// handle the upgradeToRevocableSession path on it's own | ||
if (info.sessionToken && | ||
req.url === '/upgradeToRevocableSession' && | ||
info.sessionToken.indexOf('r:') != 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't the presence of r: in the session token indicate non-legacy?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's why != 0 as if it's revocable, it's gonna be at that index.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah doh, I misread :)
Better support for upgrading to revocable session after migration has occurred.
Fixes #2255