Skip to content
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

Enable web apps to open external databases they don't own #426

Open
tahpot opened this issue May 1, 2024 · 1 comment
Open

Enable web apps to open external databases they don't own #426

tahpot opened this issue May 1, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@tahpot
Copy link
Member

tahpot commented May 1, 2024

When opening an external database as a user, it's necessary to authenticate with the database.

When in a web application, this authentication must happen via the account-web-vault flow which prompts the user to scan a QR code and have the Verida Wallet generate accessToken and refreshToken for each endpoint the connecting account uses for the requested context.

However, when opening an external database, the endpoint that requires authentication is no necessarily (in fact unlikely) one of the endpoints the account is associated with.

As such, it's necessary to make the following changes:

  1. account-web-vault support making an authentication request, which specifies storage node(s) to authenticate with for a given context
  2. client-ts support supplying an endpoint(s) when opening an external database
  3. account support connecting to an account for a specific endpoint
  4. Verida Wallet support authenticating with a storage node endpoint sent in the QR code auth request
@tahpot tahpot added the bug Something isn't working label May 1, 2024
@tahpot tahpot self-assigned this May 1, 2024
@tahpot tahpot added enhancement New feature or request and removed bug Something isn't working labels May 1, 2024
@tahpot
Copy link
Member Author

tahpot commented May 27, 2024

This scope of work is incorrect.

Instead create a new PreConfiguredAccount in @verida/account-node that allows injecting authContext configurations, but doesn't load them from anywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant