3 navsection: installguide
4 title: Install Keep-web server
7 Copyright (C) The Arvados Authors. All rights reserved.
9 SPDX-License-Identifier: CC-BY-SA-3.0
12 # "Introduction":#introduction
13 # "Configure DNS":#introduction
14 # "Configure anonymous user token.yml":#update-config
15 # "Update nginx configuration":#update-nginx
16 # "Install keep-web package":#install-packages
17 # "Start the service":#start-service
18 # "Restart the API server and controller":#restart-api
19 # "Confirm working installation":#confirm-working
21 h2(#introduction). Introduction
23 The Keep-web server provides read/write HTTP (WebDAV) access to files stored in Keep. This makes it easy to access files in Keep from a browser, or mount Keep as a network folder using WebDAV support in various operating systems. It serves public data to unauthenticated clients, and serves private data to clients that supply Arvados API tokens. It can be installed anywhere with access to Keep services, typically behind a web proxy that provides TLS support. See the "godoc page":http://godoc.org/github.com/curoverse/arvados/services/keep-web for more detail.
25 h2(#dns). Configure DNS
27 It is important to properly configure the keep-web service to so it does not open up cross-site-scripting (XSS) attacks. A HTML file can be stored in collection. If an attacker causes a victim to visit that HTML file through Workbench, it will be rendered by the browser. If all collections are served at the same domain, the browser will consider collections as coming from the same origin and thus have access to the same browsing data (such as API token), enabling malicious Javascript in the HTML file to access Arvados as the victim.
29 There are two approaches to mitigate this.
31 # The service can tell the browser that all files should go to download instead of in-browser preview, except in situations where an attacker is unlikely to be able to gain access to anything they didn't already have access to.
32 # Each each collection served by @keep-web@ is served on its own virtual host. This allows for file with executable content to be displayed in-browser securely. The virtual host embeds the collection uuid or portable data hash in the hostname. For example, a collection with uuid @xxxxx-4zz18-tci4vn4fa95w0zx@ could be served as @xxxxx-4zz18-tci4vn4fa95w0zx.collections.ClusterID.example.com@ . The portable data hash @dd755dbc8d49a67f4fe7dc843e4f10a6+54@ could be served at @dd755dbc8d49a67f4fe7dc843e4f10a6-54.collections.ClusterID.example.com@ . This requires "wildcard DNS record":https://en.wikipedia.org/wiki/Wildcard_DNS_record and "wildcard TLS certificate.":https://en.wikipedia.org/wiki/Wildcard_certificate
34 h3. Collections download URL
36 Downloads links will served from the the URL in @Services.WebDAVDownload.ExternalURL@ . The collection uuid or PDH is put in the URL path.
38 If blank, serve links to WebDAV with @disposition=attachment@ query param. Unlike preview links, browsers do not render attachments, so there is no risk of XSS.
40 If @WebDAVDownload@ is blank, and @WebDAV@ has a single origin (not wildcard, see below), then Workbench will show an error page
45 ExternalURL: <span class="userinput">https://download.ClusterID.example.com</span>
49 h3. Collections preview URL
51 Collections will be served using the URL pattern in @Services.WebDAV.ExternalURL@ . If blank, use @Services.WebDAVDownload.ExternalURL@ instead, and disable inline preview. If both are empty, downloading collections from workbench will be impossible.
53 h4. In their own subdomain
55 Collections can be served from their own subdomain:
60 ExternalURL: <span class="userinput">https://*.collections.ClusterID.example.com</span>
64 h4. Under the main domain
66 Alternately, they can go under the main domain by including @--@:
71 ExternalURL: <span class="userinput">https://*--collections.ClusterID.example.com</span>
75 h4. From a single domain
77 Serve preview links from a single domain, setting uuid or pdh in the path (similar to downloads). This configuration only allows previews of public data or collection-sharing links, because these use the anonymous user token or the token is already embedded in the URL. Authenticated requests will always result in file downloads from @Services.WebDAVDownload.ExternalURL@.
82 ExternalURL: <span class="userinput">https://collections.ClusterID.example.com</span>
92 <span class="userinput">"http://localhost:9002"</span>: {}
96 h2(#update-config). Configure anonymous user token
98 {% assign railscmd = "bundle exec ./script/get_anonymous_user_token.rb --get" %}
99 {% assign railsout = "zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz" %}
100 If you intend to use Keep-web to serve public data to anonymous clients, configure it with an anonymous token. Use the following command on the <strong>API server</strong> to create an anonymous user token. {% include 'install_rails_command' %}
104 AnonymousUserToken: <span class="userinput">"{{railsout}}"</span>
108 Set @Users.AnonymousUserToken: ""@ (empty string) or leave it out if you do not want to serve public data.
110 h3. Update nginx configuration
112 Put a reverse proxy with SSL support in front of keep-web. Keep-web itself runs on the port 25107 (or whatever is specified in @Services.Keepproxy.InternalURL@) the reverse proxy runs on port 443 and forwards requests to Keepproxy.
114 Use a text editor to create a new file @/etc/nginx/conf.d/keep-web.conf@ with the following configuration. Options that need attention are marked with “TODO”.
118 server 127.0.0.1:<span class="userinput">9002</span>;
123 server_name download.<span class="userinput">ClusterID</span>.example.com
124 collections.<span class="userinput">ClusterID</span>.example.com
125 *.collections.<span class="userinput">ClusterID</span>.example.com
126 ~.*--collections.<span class="userinput">ClusterID</span>.example.com;
128 proxy_connect_timeout 90s;
129 proxy_read_timeout 300s;
132 ssl_certificate <span class="userinput">/TODO/YOUR/PATH/TO/cert.pem</span>;
133 ssl_certificate_key <span class="userinput">/TODO/YOUR/PATH/TO/cert.key</span>;
136 proxy_pass http://keep-web;
137 proxy_set_header Host $host;
138 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
140 client_max_body_size 0;
141 proxy_http_version 1.1;
142 proxy_request_buffering off;
147 {% include 'notebox_begin' %}
148 If you restrict access to your Arvados services based on network topology -- for example, your proxy server is not reachable from the public internet -- additional proxy configuration might be needed to thwart cross-site scripting attacks that would circumvent your restrictions.
150 Normally, Keep-web accepts requests for multiple collections using the same host name, provided the client's credentials are not being used. This provides insufficient XSS protection in an installation where the "anonymously accessible" data is not truly public, but merely protected by network topology.
152 In such cases -- for example, a site which is not reachable from the internet, where some data is world-readable from Arvados's perspective but is intended to be available only to users within the local network -- the downstream proxy should configured to return 401 for all paths beginning with "/c="
153 {% include 'notebox_end' %}
155 {% assign arvados_component = 'keep-web' %}
157 {% include 'install_packages' %}
159 {% include 'start_service' %}
161 {% include 'restart_api' %}
163 h2(#confirm-working). Confirm working installation
166 $ curl -H "Authorization: Bearer $system_root_token" https://download.ClusterID.example.com/c=59389a8f9ee9d399be35462a0f92541c-53/_/hello.txt
169 If wildcard collections domains are configured:
172 $ curl -H "Authorization: Bearer $system_root_token" https://59389a8f9ee9d399be35462a0f92541c-53.collections.ClusterID.example.com/hello.txt
175 If using a single collections preview domain:
178 $ curl https://collections.ClusterID.example.com/c=59389a8f9ee9d399be35462a0f92541c-53/t=$system_root_token/_/hello.txt