-
Notifications
You must be signed in to change notification settings - Fork 161
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
Fixes various issues in authorization request handlers #133
base: master
Are you sure you want to change the base?
Conversation
this.locationLike.assign(url); | ||
resolve(null); | ||
}) | ||
.catch(error => reject(error)); |
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.
Catch and bubble up errors to avoid unhandled promise rejection.
@tikurahul could you check the PR again after my changes regarding your comments? |
@tikurahul We are interested in having this PR releases as it addresses our security concerns. |
@tikurahul please let me know if there is something holding you back merging this PR. |
@tikurahul Sorry, thank you for seeing this PR. |
Hi, do you still consider to merge this pull request as we are pretty interested in those changes? |
+1 |
any reason why this hasn't been merged? |
NodeBasedHandler
server startup error (eg:EADDRINUSE
) Uncaught error is thrown when port for notifier server is already in use #95NodeBasedHandler
only opens authorization url if server could be successfully started, to avoid leaking Tokens to another process listening on the configured port.NodeBasedHandler
now only binds to loopback (127.0.0.1) interface Notifier server should only bind to loopback interface #93