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

Proper Login Screen #120

Open
dergigi opened this issue Feb 22, 2022 · 6 comments
Open

Proper Login Screen #120

dergigi opened this issue Feb 22, 2022 · 6 comments
Labels
enhancement New feature or request security Issues related to security; could lead to loss of funds UI/UX Issue related to cosmetics, design, or user experience
Milestone

Comments

@dergigi
Copy link
Contributor

dergigi commented Feb 22, 2022

The HTTP Basic Authentication added in #75 was just a temporary solution to get the first version out the door.

We should probably implement a proper login screen just like RTL and others have it.

@dergigi dergigi added enhancement New feature or request UI/UX Issue related to cosmetics, design, or user experience security Issues related to security; could lead to loss of funds labels Feb 22, 2022
@dergigi dergigi added this to the v0.1.0 - What's in a Name? milestone Feb 22, 2022
@editwentyone
Copy link

if we implement a proper login screen, do we then need individual passwords for each wallet inside?

@ghost
Copy link

ghost commented Apr 6, 2022

Nope, this is independent from wallet passwords. UX wise it would stay the same as it is with the current Basic Authentication setup.

This would just be a screen that protects the app from unauthorized access. Everything to the right of he vertical line below would stay exactly the same as it is currently.

                           │
                           │
                           │
┌────────────────────┐     │      ┌─────────────────────────┐
│                    │     │      │                         │
│                    │     │      │                         │
│                    │     │      │                         │
│   Login Screen     │  ───┼───►  │     Wallets Screen      │ ────────► ...
│                    │     │      │                         │
│                    │     │      │                         │
└────────────────────┘     │      └─────────────────────────┘
                           │
                           │
                           │
                           │
                           │

@editwentyone
Copy link

editwentyone commented Apr 6, 2022

then why bother? I mean you can't access the wallets tu unlock them. the only option you have is to create a new wallet (until now)

why bother the normal home user to enter passwords kind of twice plus all the confusion for the normies (even 3 times, if you go through umbrel login » apps)

@ghost
Copy link

ghost commented Apr 7, 2022

Because some parts of the API (e.g. listing wallets, creating wallets) will be accessible for anyone on the internet otherwise. While, as you correctly said, funds won't be in danger since wallets are locked on Joinmarket level, imagine people harassing you by creating thousands of wallets on your node or inferring things about the way you use Joinmarket by looking at what/how many wallets you have. That's something we don't want.

We already have this flow in place. It uses HTTP Basic Authentication to implement the vertical line from the diagram. Basic Auth looks a bit old and dusted and there's no way for us to style it which is why we want to move towards an in-app login screen similar to what Thunderhub, RTL, etc. have.

@editwentyone
Copy link

editwentyone commented Apr 8, 2022

got it, thanks for the explanation. will add a screen with login prompt. its just a password field isn't it?

@editwentyone
Copy link

editwentyone commented Apr 12, 2022

I added a simple login screen and also a logout possibility on the settings screen

🎨 Figma Login
🎨 Figma Logout

image

image

@editwentyone editwentyone added this to the v0.5.0 milestone Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request security Issues related to security; could lead to loss of funds UI/UX Issue related to cosmetics, design, or user experience
Projects
Status: No status
Development

No branches or pull requests

2 participants