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

[FEATURE REQUEST] Stop authentication flow after account removal if URL is fixed #4067

Closed
8 tasks done
jesmrec opened this issue Jun 13, 2023 · 2 comments · Fixed by #4106
Closed
8 tasks done

[FEATURE REQUEST] Stop authentication flow after account removal if URL is fixed #4067

jesmrec opened this issue Jun 13, 2023 · 2 comments · Fixed by #4106
Assignees
Labels
Authentication Estimation - 2 (S) p2-high Escalation, on top of current planning, release blocker
Milestone

Comments

@jesmrec
Copy link
Collaborator

jesmrec commented Jun 13, 2023

Reference:

Current behaviour:

  1. In setup.xml set the following fields:
    • server_url -> any valid URL of a server using browser authentication
    • show_server_url_input -> false
  2. Install app and type credentials to add the account
  3. Open Manage accounts and remove account

Moved to login view and then, straight to browser

Expected: login view. Browser will be open when user clicks on CHECK SERVER (rename button?). Only if URL is fixed and hidden.

That feature was added in the first webfinger iteration (non-authenticated).

TASKS

  • Research (if needed)
  • Create branch feature/stop_auth_flow_url_fixed
  • Development tasks
    • Set conditions to continue or not with the authentication flow
  • Code review and apply changes requested
  • Design test plan
  • QA
  • Merge branch feature/stop_auth_flow_url_fixed into master
@jesmrec jesmrec added this to the 4.1 - Next milestone Jun 13, 2023
@jesmrec jesmrec added p2-high Escalation, on top of current planning, release blocker Sprint labels Jul 10, 2023
@JuancaG05 JuancaG05 self-assigned this Jul 20, 2023
@JuancaG05
Copy link
Collaborator

To solve this I tried to keep the current flow (browser opens automatically) in all cases except when coming from removing the only account logged in the app in the accounts management screen. However, it seems that all cases in which we launch the login screen use a same common method for it, and cannot distinguish if I come from one screen or another, which was my original idea.

So, a possible solution could be removing the automatic opening of the browser when there is a fixed URL, the behaviour we had some versions ago (automatic opening was introduced as an improvement to save 1 click and make the login process smoother). What do you think @michaelstingl?

@michaelstingl
Copy link
Contributor

So, a possible solution could be removing the automatic opening of the browser when there is a fixed URL, the behaviour we had some versions ago (automatic opening was introduced as an improvement to save 1 click and make the login process smoother). What do you think @michaelstingl?

Yes, should solve it 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Authentication Estimation - 2 (S) p2-high Escalation, on top of current planning, release blocker
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants