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

After Shared Snapshot Link redirects to login page and user logs in, should redirect to appropriate project. #2014

Open
6 tasks
entrotech opened this issue Jan 6, 2025 · 0 comments

Comments

@entrotech
Copy link
Member

entrotech commented Jan 6, 2025

Overview

We need to have the user redirected to the snapshot link they used to access the TDM site, so that users don't have to log in and then go find the link and paste it into the browser.

Details

When a registered user receives a link to a shared snapshot, they can paste the link into a browser to view the snapshot. However, if they are not already logged in to the application, they are redirected to the login page to log in. In this case, the login page should remember that they were trying to navigate to the snapshot, and redirect back to the snapshot path after a successful login.

more Explanation

If the user is already logged into the application in the current browser under the email associated with the snapshot, a link like https://tdm-dev.azurewebsites.net/projects/254 will work. However if they are logged in with a different account, or not logged in at all, they are redirected to the login page. Once they successfully log in, they are normally redirected to the first page of the "Create Project" wizard, but in this particular case they should be re-directed to the originally requested url, which should now succeed because they are logged in with an account that is authorized to access the snapshot.

Action Items

  • Modify the initializeEngine method in the TdmCalculationContainer component such that under the circumstances described above, the redirect to /unauthorized is changed to redirect to /login?url=, where is the originally requested url.
  • Modify the login component such that, if the path query string parameter is supplied, the application redirects to that path after a successful login. Implementing the url query string parameter generically like this will allow for other situations where redirect after a successful login is needed.
  • Review with product and design. Update if needed based on feedback
  • Once finalized, add before and after images to the staging deck on this slide
  • Get Stakeholder sign-off via the stakeholder meeting slide deck.

Resources/Instructions

REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

1 participant