Actions
Bug #17314
open
[API] [controller] [Workbench] 404 on foreign user UUID in admin interface
Story points:
-
Release:
Release relationship:
Auto
Description
9tee4 and ce8i5 are configured in a peer federation. 9tee4:
RemoteClusters:
9tee4:
Host: 9tee4.arvadosapi.com
Proxy: true
ActivateUsers: true
tordo:
Host: tordo.arvadosapi.com
Proxy: true
ActivateUsers: true
ce8i5:
Host: ce8i5.arvadosapi.com
Proxy: true
ActivateUsers: true
...
Login:
Google:
Enable: true
AlternateEmailAddresses: true
...
And ce8i5 is configured like this:
RemoteClusters:
ce8i5:
Host: ce8i5.arvadosapi.com
Proxy: true
ActivateUsers: true
tordo:
Host: tordo.arvadosapi.com
Proxy: true
ActivateUsers: true
9tee4:
Host: 9tee4.arvadosapi.com
Proxy: true
ActivateUsers: true
...
Login:
LoginCluster: ce8i5
Google:
Enable: true
AlternateEmailAddresses: true
...
Using workbench 1, in the admin interface, users from the peer clusters are listed. The UUIDs are showing as 'active' in the list.
But clicking on the UUID it self results in a 404, e.g.
https://workbench.9tee4.arvadosapi.com/users/ce8i5-tpzed-o4njwilpp4ov286and
https://workbench.ce8i5.arvadosapi.com/users/9tee4-tpzed-c2n6rni0dblbnfa
Updated by Ward Vandewege about 5 years ago
- Subject changed from [API] [controller] [Workbench] 404 on foreign user uuid in admin interface to [API] [controller] [Workbench] 404 on foreign user UUID in admin interface
Updated by Ward Vandewege about 5 years ago
- Related to Bug #16974: Explain RemoteClusters.Proxy and .ActivateUsers better added
Updated by Ward Vandewege about 5 years ago
- Related to Feature #17313: [Documentation] improve federation documentation added
Updated by Peter Amstutz over 4 years ago
- Target version deleted (
To Be Groomed)
Actions