-
Notifications
You must be signed in to change notification settings - Fork 194
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
feat: Alby OAuth Connector #2399
Conversation
…ialogue using lndhub backend currently signed-off-by:pavanj914@gmail.com
pass connector field to accountContext use it to validate that account is alby or not eliminate alias hack to check alby account which can be changed signed-off-by:pavanj914@gmail.com
signed-off-by: pavanj914@gmail.com
signed-off-by: pavanj914@gmail.com
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
🚀 Thanks for the pull request! Here are the current build files for testing: Download and unzip the file for your browser. Refer to the readme for detailed install instructions. This build is brought to you by: Want to sponsor the next build? send some sats to ⚡️builds@getalby.com (don't forget to provide your name) Don't forget: keep earning sats! |
… connector without launching oauth flow
refactor generation of access token from oauth result
Some issues found so far:
|
Chore/web auth prototype feedback
…/lightning-browser-extension into web-auth-prototype
const response = await msg.request( | ||
"sendPayment", | ||
{ paymentRequest: paymentRequest }, | ||
{ | ||
origin: navState.origin, | ||
} | ||
); | ||
if (response.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.
Double check if that is needed? Is that really the case for existing connectors too, that no errors would be shown?
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.
There are multiple places where an error is returned, and the sendPayment action is wrapped in try/catch. I think we need this check, I don't understand how it worked before.
…ng-browser-extension into web-auth-prototype
Co-authored-by: René Aaron <100827540+reneaaron@users.noreply.github.com>
Wallet Interface with Oauth security
Type of change
feat
: New feature (non-breaking change which adds functionality)Screenshots of the changes [optional]
Alby.OAUTH.CONNECTOR.mp4
Checklist