Actions
Bug #15255
closed
[workbench2] 401 retrieving user info on c97qk
Story points:
-
Release:
Release relationship:
Auto
Description
Testing latest workbench2 on https://workbench2.c97qk.arvadosapi.com, when navigating to a project, it is failing to load the project contents → this is due to getting a 401 retrieving user info and apparently being logged out (and poor error reporting in wb2).
Updated by Peter Amstutz over 5 years ago
- Subject changed from [workbench2] Project navigation not working to [workbench2] Getting 401
- Description updated (diff)
Updated by Peter Amstutz over 5 years ago
- Subject changed from [workbench2] Getting 401 to [workbench2] 401 retrieving user info on c97qk
Updated by Peter Amstutz over 5 years ago
- Status changed from New to In Progress
- Assigned To set to Peter Amstutz
Updated by Tom Morris over 5 years ago
- Target version changed from To Be Groomed to 2019-05-22 Sprint
Updated by Peter Amstutz over 5 years ago
This is a bug in the iframe based federated login.
The other clusters are not publishing a workbench2 URL.
The iframe loads workbench, but because workbench2 URL is blank, it is calling /fedtoken on the local workbench. This sets the token to a salted token (which is intended for the remote cluster and not usable on the home cluster).
Code fix: don't create iframes if workbench2 is empty.
Ops fix configuration to publish workbench2 URL.
Updated by Tom Morris over 5 years ago
- Target version changed from 2019-05-22 Sprint to 2019-06-05 Sprint
Updated by
Updated by Peter Amstutz over 5 years ago
- Status changed from In Progress to Resolved
Actions