-
Notifications
You must be signed in to change notification settings - Fork 309
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
Add client secret to refreshToken and remove ID token validation #433
Conversation
expect(request.isDone()).to.be.true; | ||
done(); | ||
}) | ||
.catch(done); |
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.
wouldn't calling done
imply the test is over successfully? And if so, I don't think we want that for the case where something goes wrong like here that an exception is thrown.
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.
Honestly, I'm not totally sure. This is only one of a few tests for refreshToken
and we're just looking for something specific, that the secret is there.
@lbalmaceda - Ready for you again! |
Changes
References
#432
Testing