X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/3677f1aea53f1a04811270f98a681dbcd6002e67..cc952178056bf6d29471f6986306fb673dcf394a:/doc/install/install-sso.html.textile.liquid?ds=sidebyside diff --git a/doc/install/install-sso.html.textile.liquid b/doc/install/install-sso.html.textile.liquid index a8e39b2f68..b2a4f671a3 100644 --- a/doc/install/install-sso.html.textile.liquid +++ b/doc/install/install-sso.html.textile.liquid @@ -1,28 +1,41 @@ --- layout: default navsection: installguide -title: Install Single Sign On (SSO) server +title: Install the Single Sign On (SSO) server ... +{% comment %} +Copyright (C) The Arvados Authors. All rights reserved. -h2(#dependencies). Install dependencies +SPDX-License-Identifier: CC-BY-SA-3.0 +{% endcomment %} + +h2(#dependencies). Install prerequisites + +The Arvados package repository includes an SSO server package that can help automate much of the deployment. h3(#install_ruby_and_bundler). Install Ruby and Bundler {% include 'install_ruby_and_bundler' %} +h3(#install_web_server). Set up a Web server + +For best performance, we recommend you use Nginx as your Web server frontend with a Passenger backend to serve the SSO server. The Passenger team provides "Nginx + Passenger installation instructions":https://www.phusionpassenger.com/library/walkthroughs/deploy/ruby/ownserver/nginx/oss/install_passenger_main.html. + +Follow the instructions until you see the section that says you are ready to deploy your Ruby application on the production server. + h2(#install). Install the SSO server On a Debian-based system, install the following package: -
~$ sudo apt-get arvados-sso
+
~$ sudo apt-get install arvados-sso-server
 
On a Red Hat-based system, install the following package: -
~$ sudo yum install arvados-sso
+
~$ sudo yum install arvados-sso-server
 
@@ -37,7 +50,7 @@ The package has installed three configuration files in @/etc/arvados/sso@:
-The SSO server runs from the @/var/www/arvados-sso/current/@ directory. The configuration files in @/etc/arvados/sso/@ are symlinked to @/var/www/arvados-sso/current/config/application.yml@, @/var/www/arvados-sso/current/config/database.yml@ and @/var/www/arvados-sso/current/config/environments/production.rb@. +The SSO server runs from the @/var/www/arvados-sso/current/@ directory. The files @/var/www/arvados-sso/current/config/application.yml@, @/var/www/arvados-sso/current/config/database.yml@ and @/var/www/arvados-sso/current/config/environments/production.rb@ are symlinked to the configuration files in @/etc/arvados/sso/@. The SSO server reads the @config/application.yml@ file, as well as the @config/application.defaults.yml@ file. Values in @config/application.yml@ take precedence over the defaults that are defined in @config/application.defaults.yml@. The @config/application.yml.example@ file is not read by the SSO server and is provided for installation convenience only. @@ -48,7 +61,7 @@ h3(#uuid_prefix). uuid_prefix Generate a uuid prefix for the single sign on service. This prefix is used to identify user records as originating from this site. It must be exactly 5 lowercase ASCII letters and/or digits. You may use the following snippet to generate a uuid prefix: -
$ ruby -e 'puts "#{rand(2**64).to_s(36)[0,5]}"'
+
~$ ruby -e 'puts "#{rand(2**64).to_s(36)[0,5]}"'
 abcde
 
@@ -59,7 +72,7 @@ h3(#secret_token). secret_token Generate a new secret token for signing cookies: -
$ ruby -e 'puts rand(2**400).to_s(36)'
+
~$ ruby -e 'puts rand(2**400).to_s(36)'
 zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
 
@@ -69,85 +82,86 @@ There are other configuration options in @/etc/arvados/sso/application.yml@. See h2(#database). Set up the database -Generate a new database password. Nobody ever needs to memorize it or type it, so make a strong one: +Configure the SSO server to connect to your database by updating @/etc/arvados/sso/database.yml@. Replace the @xxxxxxxx@ database password placeholder with the "password you generated during database setup":install-postgresql.html#sso. Be sure to update the @production@ section. -
$ ruby -e 'puts rand(2**128).to_s(36)'
-abcdefghijklmnopqrstuvwxyz012345689
+
~$ editor /etc/arvados/sso/database.yml
 
-Configure the SSO server to connect to your database by updating @/etc/arvados/sso/database.yml@. Replace the @xxxxxxxx@ database password placeholder with the new password you generated above. Be sure to update the @production@ section. - - -
$ edit /etc/arvados/sso/database.yml
-
+h2(#reconfigure_package). Reconfigure the package -Create a new database user with permission to create its own databases. +{% assign railspkg = "arvados-sso-server" %} +{% include 'install_rails_reconfigure' %} - -
$ sudo -u postgres createuser --createdb --encrypted -R -S --pwprompt arvados_sso
-Enter password for new role: paste-database-password-you-generated
-Enter it again: paste-database-password-you-generated
-
+h2(#client). Create arvados-server client -Rails will take care of creating the database, based on the information from @/etc/arvados/sso/database.yml@. +{% assign railshost = "" %} +{% assign railsdir = "/var/www/arvados-sso/current" %} +Use @rails console@ to create a @Client@ record that will be used by the Arvados API server. {% include 'install_rails_command' %} -Alternatively, if the database user you intend to use for the SSO server should not be allowed to create new databases, the user and the database can be created like this: +Enter the following commands at the console. The values that appear after you assign @app_id@ and @app_secret@ correspond to the values for @sso_app_id@ and @sso_app_secret@, respectively, in the "API server's SSO settings":install-api-server.html#omniauth. -
$ sudo -u postgres createuser --encrypted -R -S --pwprompt arvados_sso
-Enter password for new role: paste-database-password-you-generated
-Enter it again: paste-database-password-you-generated
-$ sudo -u postgres createdb arvados_sso_production -E UTF8 -O arvados_sso -T template0
-
+
:001 > c = Client.new
+:002 > c.name = "joshid"
+:003 > c.app_id = "arvados-server"
+:004 > c.app_secret = rand(2**400).to_s(36)
+=> "save this string for your API server's sso_app_secret"
+:005 > c.save!
+:006 > quit
+
+ -{% include 'notebox_begin' %} +h2(#configure_web_server). Configure your web server + +Edit the http section of your Nginx configuration to run the Passenger server and act as a frontend for it. You might add a block like the following, adding SSL and logging parameters to taste: -If you are installing on CentOS6, you will need to modify PostgreSQL's configuration to allow password authentication for local users. The default configuration allows 'ident' only. The following commands will make the configuration change, and restart PostgreSQL for it to take effect. -
-
$ sudo sed -i -e "s/127.0.0.1\/32          ident/127.0.0.1\/32          md5/" /var/lib/pgsql/data/pg_hba.conf
-$ sudo sed -i -e "s/::1\/128               ident/::1\/128               md5/" /var/lib/pgsql/data/pg_hba.conf
-$ sudo service postgresql restart
-
-
-{% include 'notebox_end' %} +
server {
+  listen 127.0.0.1:8900;
+  server_name localhost-sso;
 
-h2(#reconfigure_package). Reconfigure the package
+  root   /var/www/arvados-sso/current/public;
+  index  index.html;
 
-Now that the @/etc/arvados/sso/application.yml@ and @/etc/arvados/sso/database.yml@ files have been updated, we need to reconfigure our installed package. Doing so will create and/or initialize the database and precompile the assets.
+  passenger_enabled on;
+  # If you're not using RVM, comment out the line below.
+  passenger_ruby /usr/local/rvm/wrappers/default/ruby;
+}
 
-On a Debian-based system:
+upstream sso {
+  server     127.0.0.1:8900  fail_timeout=10s;
+}
 
-
-
~$ sudo dpkg-reconfigure arvados-sso
-
-
+proxy_http_version 1.1; -On a Red Hat-based system, we need to reinstall the package instead: +server { + listen [your public IP address]:443 ssl; + server_name auth.your.domain; - -
~$ sudo yum reinstall arvados-sso
-
-
+ ssl on; + ssl_certificate /YOUR/PATH/TO/cert.pem; + ssl_certificate_key /YOUR/PATH/TO/cert.key; -h2(#client). Create arvados-server client + index index.html; -Use @rails console@ to create a @Client@ record that will be used by the Arvados API server. The values of @app_id@ and @app_secret@ correspond to the values for @sso_app_id@ and @sso_app_secret@ in the "API server's SSO settings.":install-api-server.html#omniauth + location / { + proxy_pass http://sso; + proxy_redirect off; + proxy_connect_timeout 90s; + proxy_read_timeout 300s; - -
$ ruby -e 'puts rand(2**400).to_s(36)'
-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-$ RAILS_ENV=production bundle exec rails console
-:001 > c = Client.new
-:002 > c.name = "joshid"
-:003 > c.app_id = "arvados-server"
-:004 > c.app_secret = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
-:005 > c.save!
-:006 > quit
+    proxy_set_header      X-Forwarded-Proto https;
+    proxy_set_header      Host $http_host;
+    proxy_set_header      X-Real-IP $remote_addr;
+    proxy_set_header      X-Forwarded-For $proxy_add_x_forwarded_for;
+  }
+}
 
+Finally, restart Nginx and your Arvados SSO server should be up and running. You can verify that by visiting the URL you configured your Nginx web server to listen on in the server section above (port 443). Read on if you want to configure your Arvados SSO server to use a different authentication backend. + h2(#authentication_methods). Authentication methods Authentication methods are configured in @application.yml@. Currently three authentication methods are supported: local accounts, LDAP, and Google+. If neither Google+ nor LDAP are enabled, the SSO server defaults to local user accounts. Only one authentication mechanism should be in use at a time. @@ -168,11 +182,12 @@ There are two configuration options for local accounts: For more information about configuring backend support for sending email (required to send email confirmations) see "Configuring Action Mailer":http://guides.rubyonrails.org/configuring.html#configuring-action-mailer -If @allow_account_registration@ is false, you may manually create local accounts on the SSO server from the rails console: +If @allow_account_registration@ is false, you may manually create local accounts on the SSO server from the Rails console. {% include 'install_rails_command' %} + +Enter the following commands at the console. -
~/sso-devise-omniauth-provider$ RAILS_ENV=production bundle exec rails console
-:001 > user = User.new(:email => "test@example.com")
+
:001 > user = User.new(:email => "test@example.com")
 :002 > user.password = "passw0rd"
 :003 > user.save!
 :004 > quit
@@ -221,71 +236,12 @@ In order to use Google+ authentication, you must use the "---YOUR---CLIENT---ID---HERE--"-
   google_oauth2_client_secret: "---YOUR---CLIENT---SECRET---HERE--"-
- -h2(#start). Set up a Web server - -For best performance, we recommend you use Nginx as your Web server front-end, with a Passenger backend to serve the SSO server. To do that: - - -
    -
  1. Install Nginx and Phusion Passenger.
  2. - -
  3. Edit the http section of your Nginx configuration to run the Passenger server, and act as a front-end for it. You might add a block like the following, adding SSL and logging parameters to taste:

    - -
    server {
    -  listen 127.0.0.1:8900;
    -  server_name localhost-sso;
    -
    -  root   /var/www/arvados-sso/current/public;
    -  index  index.html;
    -
    -  passenger_enabled on;
    -  # If you're not using RVM, comment out the line below.
    -  passenger_ruby /usr/local/rvm/wrappers/default/ruby;
    -}
    -
    -upstream sso {
    -  server     127.0.0.1:8900  fail_timeout=10s;
    -}
    -
    -proxy_http_version 1.1;
    -
    -server {
    -  listen       [your public IP address]:443 ssl;
    -  server_name  auth.your.domain;
    -
    -  ssl on;
    -  ssl_certificate     /YOUR/PATH/TO/cert.pem;
    -  ssl_certificate_key /YOUR/PATH/TO/cert.key;
    -
    -  index  index.html;
    -
    -  location / {
    -    proxy_pass            http://sso;
    -    proxy_redirect        off;
    -    proxy_connect_timeout 90s;
    -    proxy_read_timeout    300s;
    -
    -    proxy_set_header      X-Forwarded-Proto https;
    -    proxy_set_header      Host $http_host;
    -    proxy_set_header      X-Real-IP $remote_addr;
    -    proxy_set_header      X-Forwarded-For $proxy_add_x_forwarded_for;
    -  }
    -}
    -
    -
  4. - -
  5. Restart Nginx.
  6. - -
- -