-
Notifications
You must be signed in to change notification settings - Fork 59
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
Login and Logout Redirects #10756
Comments
Copied from #10248 Use Case:
|
Copied from #10248 Note: Staff flows also need the parallel behaviour for their respective dashboards. |
@lmcclung @Kaineatthelab Is this required for MVP on Monday? |
@severinbeauvais ideally but lower priority |
@chdivyareddy FYI ^^^ (I will work on syncing Scott's spreadsheet with this Story and its tickets today.) |
@severinbeauvais Sounds good:) |
I have finished this Story (and moved it to Epic in Progress) and created linked tickets for the work, which can now be prioritized. |
Changed to lower priority than account ID issues per PO sync today. |
See also Scott's spreadsheet.
Problems to solve:
(AC from design tickets #10231, #10633 and #10656)
As a BC Registries user,
When I log out of my account for the day,
Then I want to be redirected to the appropriate logged out page and know that I have successfully logged out.
Solution: if a user logs out of any dashboard or app page, redirect them to a generic login page. It has already been created in ticket #10248 for Business Registry and PPR and in ticket #10795 for BC Registries. Now we need to also include the functionality for Business Registry apps. (Marketing pages are the exception: if a user logs out of a marketing page, redirect them to the logged out version of that marketing page.)
As a BC Registries user,
When I access a bookmarked BC Registries (including Business Registry and PPR) page from a non-logged-in state,
Then I want the ability to log on using IDIR, BC Services Card App, or BCeID.
Solution: if a user bookmarks the staff/uber dashboard or app page in a logged out state, direct users to the generic login page. If possible (ie, nice to have), after login, redirect user back to original bookmark (dashboard or app page). This is now supported by #10905, though the app needs to send a redirect parameter (#10853).
As a BC Registries user,
When I log in to a page that I don't have access to,
Then I want to see an appropriate message and/or be redirected to the BC Registries dashboard.
Solution: need design - see #10656
Dashboards include:
Marketing pages include:
App pages include:
Use Cases:
Logout Behaviours
from BC Registries Dashboard, redirect to BC Registries Account Login pagedone in Registry UI: logout behaviours #10795from BC Registries marketing page, redirect to BC Registries marketing page (logged out version)done in Registry UI - handle login/logout states #10697from PPR marketing page, redirect to PPR marketing page (logged out version)done in Registry UI: logout behaviours #10795from Business Registry marketing page, redirect to Business Registry marketing page (logged out version)existing behaviourBookmark / Login Behaviours
(In most cases, after logging in, go to BC Registries dashboard
("staff" = IDIR with
staff
role)("SBC staff" = IDIR with
gov_account_user
role and "Service BC" in branch name)("not staff" = none of the above, for example, BCSC, BCeID or other IDIRs)
from Business Registry marketing page, logging in as "staff", redirect to Staff Dashboardexisting behaviour.
.
from Staff Dashboard, logging in as "staff", redirect to Staff Dashboardexisting behaviour.
from My Business Registry, with valid credentials, redirect to My Business Registry- existing behaviour.
from Filings UI, just show error dialog; on Exit, go to Business Registry marketing page- existing behaviourfrom Create UI, just show error dialog; on Exit, go to Business Registry marketing page- existing behaviourfrom Edit UI, just show error dialog; on Exit, go to Business Registry marketing page- existing behaviour.
Test Notes
Please test will all variations of logins, including:
The text was updated successfully, but these errors were encountered: