[ARVADOS] updated: b3bccdb71967ea963e9a747a3521bd99e33e12a4

git at public.curoverse.com git at public.curoverse.com
Tue Mar 3 10:17:44 EST 2015


Summary of changes:
 doc/install/install-manual-prerequisites.html.textile.liquid | 3 ++-
 doc/install/install-sso.html.textile.liquid                  | 4 ++--
 2 files changed, 4 insertions(+), 3 deletions(-)

       via  b3bccdb71967ea963e9a747a3521bd99e33e12a4 (commit)
      from  c3be77dc1329ac775c686fd40ca1014a799a3a79 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit b3bccdb71967ea963e9a747a3521bd99e33e12a4
Author: Ward Vandewege <ward at curoverse.com>
Date:   Tue Mar 3 10:16:23 2015 -0500

    Follow the naming conventions for hostnames; add SSO server as a
    public-facing service that requires an SSL certificate.
    
    refs #5322

diff --git a/doc/install/install-manual-prerequisites.html.textile.liquid b/doc/install/install-manual-prerequisites.html.textile.liquid
index e5b28d9..5fe214e 100644
--- a/doc/install/install-manual-prerequisites.html.textile.liquid
+++ b/doc/install/install-manual-prerequisites.html.textile.liquid
@@ -34,7 +34,7 @@ You may also use a different method to pick the unique identifier. The unique id
 
 h2. SSL certificates
 
-There are four public-facing services that will require an SSL certificate. If you do not have official SSL certificates, you can use self-signed certificates. By convention, we use the following hostname pattern:
+There are five public-facing services that will require an SSL certificate. If you do not have official SSL certificates, you can use self-signed certificates. By convention, we use the following hostname pattern:
 
 <div class="offset1">
 table(table table-bordered table-condensed).
@@ -43,4 +43,5 @@ table(table table-bordered table-condensed).
 |Arvados Websockets endpoint|ws. at uuid_prefix@.your.domain|
 |Arvados Keepproxy server|keep. at uuid_prefix@.your.domain|
 |Arvados Workbench|workbench. at uuid_prefix@.your.domain|
+|Arvados SSO Server|auth.your.domain|
 </div>
diff --git a/doc/install/install-sso.html.textile.liquid b/doc/install/install-sso.html.textile.liquid
index c56afea..4f6a977 100644
--- a/doc/install/install-sso.html.textile.liquid
+++ b/doc/install/install-sso.html.textile.liquid
@@ -78,10 +78,10 @@ Instead of relying on an upstream authentication such as Google, you can create
 
 To log in using a manually created account:
 
-# Go to https://your-sso-server.hostname.com/users/sign_in
+# Go to https://auth.your.domain/users/sign_in
 # Enter the email address and password and click on "Sign in"
 # You will arrive at a page "You are now signed in as test at example.com"
-# Go to https://workbench.your-arvados-instance.hostname.com/
+# Go to https://workbench.@uuid_prefix@.your.domain/
 # Click on the Workbench "Log in" button.
 # You should now be logged in to Workbench.  Confirm by looking for the email address displayed in the upper right.
 

-----------------------------------------------------------------------


hooks/post-receive
-- 




More information about the arvados-commits mailing list