Bug #17314
Updated by Ward Vandewege about 4 years ago
9tee4 and ce8i5 are configured in a peer federation. 9tee4:
<pre>
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
...
</pre>
<pre>
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
...
</pre>
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-o4njwilpp4ov286
and
https://workbench.ce8i5.arvadosapi.com/users/9tee4-tpzed-c2n6rni0dblbnfa