[ARVADOS] created: 2.1.0-312-g060e9a90d

Git user git at public.arvados.org
Mon Feb 1 18:08:32 UTC 2021

        at  060e9a90dcb602e3c43098ec7c5fb3002cc11597 (commit)

commit 060e9a90dcb602e3c43098ec7c5fb3002cc11597
Author: Nico Cesar <nico at nicocesar.com>
Date:   Mon Feb 1 13:07:57 2021 -0500

    Doc update: remote clusters and active users
    Arvados-DCO-1.1-Signed-off-by: Nico Cesar <nico at curii.com>

diff --git a/doc/admin/federation.html.textile.liquid b/doc/admin/federation.html.textile.liquid
index eddd247e9..2abd20151 100644
--- a/doc/admin/federation.html.textile.liquid
+++ b/doc/admin/federation.html.textile.liquid
@@ -38,6 +38,8 @@ Similar settings should be added to @clsr2@ & @clsr3@ hosts, so that all cluster
 The @ActivateUsers@ setting indicates whether users from a given cluster are automatically activated or they require manual activation.  User activation is covered in more detail in the "user activation section":{{site.baseurl}}/admin/activation.html.  In the current example, users from @clsr2@ would be automatically, activated, but users from @clsr3@ would require an admin to activate the account.
+Before activating users in the later example, @clsr1@ will have a list of users from @clsr3 at . But trying to access to those UUIDs in @clsr1@ will produce a HTTP 404 until activated. 
 h2(#LoginCluster). User management
 A federation of clusters can be configured to use a separate user database per cluster, or delegate a central cluster to manage the database.



More information about the arvados-commits mailing list