Bug #14551: [Workbench] As an admin, using the "Log in as..." button uses v1 tokens - Arvados

Actions

Copy link

Bug #14551

closed

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

Added by Lucas Di Pentima about 6 years ago. Updated almost 6 years ago.

Status:

Resolved

Priority:

Normal

Assigned To:

Lucas Di Pentima

Category:

Target version:

2018-12-12 Sprint

Start date:

12/04/2018

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

Story points:

Release:

Arvados 1.3

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 1 (0 open — 1 closed)

Actions

Copy link

Updated by Lucas Di Pentima about 6 years ago

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

Actions

Copy link

Updated by Lucas Di Pentima about 6 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.

Actions

Copy link

Updated by Lucas Di Pentima about 6 years ago

Status changed from New to In Progress

Actions

Copy link

Updated by Peter Amstutz about 6 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 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.

Actions

Copy link