Bug #14551

[Workbench] As an admin, using the "Log in as..." button uses v1 tokens

Added by Lucas Di Pentima about 1 year ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
12/04/2018
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release:
Release relationship:
Auto

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.


Subtasks

Task #14556: Review 14551-wb-login-as-tokenResolvedLucas Di Pentima

Associated revisions

Revision 8f924c10
Added by Lucas Di Pentima about 1 year ago

Merge branch '14551-wb-login-as-token'
Closes #14551

Arvados-DCO-1.1-Signed-off-by: Lucas Di Pentima <>

History

#1 Updated by Lucas Di Pentima about 1 year ago

  • Assigned To set to Lucas Di Pentima
  • Target version set to 2018-12-12 Sprint

#2 Updated by Lucas Di Pentima about 1 year 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.

#3 Updated by Lucas Di Pentima about 1 year ago

  • Status changed from New to In Progress

#4 Updated by Peter Amstutz about 1 year 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 sudo method 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.

#6 Updated by Lucas Di Pentima about 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

#7 Updated by Tom Morris 10 months ago

  • Release set to 14

Also available in: Atom PDF