-
Notifications
You must be signed in to change notification settings - Fork 268
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
fix issues with refresh token #832
Conversation
Codecov Report
@@ Coverage Diff @@
## master #832 +/- ##
==========================================
- Coverage 91.70% 91.45% -0.25%
==========================================
Files 114 116 +2
Lines 3268 3313 +45
Branches 679 688 +9
==========================================
+ Hits 2997 3030 +33
- Misses 271 283 +12
Continue to review full report at Codecov.
|
lib/TokenManager.ts
Outdated
@@ -359,19 +353,15 @@ export class TokenManager { | |||
this.emitRemoved(key, removedToken); | |||
} | |||
|
|||
// TODO: these methods are redundant and can be removed in the next major version |
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.
let's add a jira to track it.
return this.sdk.token.renew(token); | ||
} | ||
validateToken(token: Token) { |
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.
also remove this one in 6.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.
Missing changelog
- do not try to renew the refresh token - catch refresh token failure and remove token - prevent invalid refresh tokens from being stored
f94f167
to
802a128
Compare
|
||
- [#832](https://github.com/okta/okta-auth-js/pull/832) Fixes issues with refresh tokens | ||
|
||
## 5.1.1 |
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.
Thanks for adding all those changelogs, I'll just close my PR #835
@@ -45,7 +45,7 @@ Feature: Multi-Factor Authentication with Password and SMS | |||
When She selects SMS from the list | |||
And She inputs a invalid phone number | |||
And She selects "Receive a Code" | |||
Then she should see a message "Unable to initiate factor enrollment: Invalid Phone Number." |
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.
probably search the error message in the code base, looks like still missing one e2e test case and some unit tests (probably not necessary).
- do not try to renew the refresh token - catch refresh token failure and remove token - prevent invalid refresh tokens from being stored fix: support rotating refresh tokens Update string for phone enroll error OKTA-329744 update error msg OKTA-403154 <<<Jenkins Check-In of Tested SHA: 5673490 for eng_productivity_ci_bot_okta@okta.com>>> Artifact: okta-auth-js Files changed count: 31 PR Link: "#832"
#738
#747
#784
OKTA-399459
OKTA-400565
OKTA-397735
OKTA-403154