Bug #14551
closed
[Workbench] As an admin, using the "Log in as..." button uses v1 tokens
Description
When logging in as a user from an admin account, the button uses a v1 token, so that's what the admin-logged-as-user gets when visiting the "Current token" page.
Updated by Lucas Di Pentima over 5 years ago
- Assigned To set to Lucas Di Pentima
- Target version set to 2018-12-12 Sprint
Updated by Lucas Di Pentima over 5 years ago
Fix at 2909f39ea214bc5b06ceeeb8d367db37a97e2197 - branch 14551-wb-login-as-token
Test run: https://ci.curoverse.com/job/developer-run-tests/985/
The sudo method now uses a v2 token to perform the login procedure.
Updated by Lucas Di Pentima over 5 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz over 5 years ago
Lucas Di Pentima wrote:
Fix at 2909f39ea214bc5b06ceeeb8d367db37a97e2197 - branch
14551-wb-login-as-token
Test run: https://ci.curoverse.com/job/developer-run-tests/985/The
sudomethod now uses a v2 token to perform the login procedure.
This LGTM, but you have two workbench integration failures. They are PhantomJS errors so maybe they are not real, but we should probably make sure it passes before merging.
Updated by Lucas Di Pentima over 5 years ago
Re-ran wb integration tests here: https://ci.curoverse.com/job/developer-run-tests-apps-workbench-integration/1024/ - all ok
Updated by Lucas Di Pentima over 5 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|8f924c10a36dc073c33f390eee6a2d2cd069859f.
Updated by Tom Morris