Workflows (possibly tools) cached through logout and login via google

Bug Report

Expected behaviour

Should see workflows for user 2 after logging out using user 1 and logging in via user 2

Actual behaviour

After switching logins to user 2, see workflows for user 1, but I can’t interact with them presumably because I have no rights.

Steps to Reproduce

Basically as described, although note the need for step 3:

1. Logout and Reload, to start from a clean slate
2. Login as user 1
3. Click on My Workflows
4. Logout
5. Login as user 2
6. Open Chrome Dev Tools
7. Click on My Workflows. You’ll see a 403 error for https://staging.dockstore.org/api/users/{wrong user}/workflows

┆Issue is synchronized with this Jira Bug ┆Issue Number: DOCK-77 ┆Sprint: Backlog ┆Issue Type: Bug

[coverbeck]

Update 2: More than one instance of UserService is being created, and that’s what’s leading to the problem; the code would work if UserService were a singleton. I believe this has to do something with modules and lazy loading. Investigating using forRoot(), but still coming up to speed on it.

[denis-yuen]

A bit of a smoking gun, the GUI calls https://staging.dockstore.org/api/users/{wrong user}/workflows but calls https://staging.dockstore.org/api/users/{correct user}/workflows after a hard refresh