Project

General

Profile

Actions

Bug #16853

open

[arvbox] various bugs

Added by Ward Vandewege almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

  • workbench 1 "Arvados test login" form looks super ugly, completely unstyled. Should we make wb2 the default, at least in the demo?
  • workbench 1 login form gives no indication of what to do for a brand new arvbox. Only when clicking the "Log in" button (without providing username/password) does the help text appear that says
  The "test login" users are defined in Clusters.[ClusterID].Login.Test.Users section of config.yml
If you are using arvbox, use "arvbox adduser" to add users." 
  • workbench 1/2 login forms say "username" but they really want the email field as per
  $ ./arvbox adduser
/usr/local/lib/arvbox/edit_users.py <path/to/config.yaml> <clusterid> add <username> <email> [pass]
                                    <path/to/config.yaml> <clusterid> remove <username>
                                    <path/to/config.yaml> <clusterid> list
  • workbench 2 is using a token that is not attached to a privileged user, so the "Current token" in the dropdown gives the error "Forbidden: this API client cannot manipulate other clients' access tokens. (req-750algt6pabl12xbbqgg)"

Related issues

Related to Arvados - Bug #16831: arvbox and bundle errorsResolvedWard Vandewege09/21/2020

Actions
Actions

Also available in: Atom PDF