Update README.md

docs/system-admin-guide/authentication/saml/README.md

@@ -17,33 +17,29 @@ You can integrate your active directory or other SAML compliant identity provide
 
 ### 1: Configuring the SAML integration
 
-The configuration can be provided in one of three ways:
+The configuration can be provided in one of two ways:
 
-* `configuration.yml` file (1.1)
+* `config/plugins/auth_saml/settings.yml` file (1.1)
 
 * Environment variables (1.2)
 
+* Settings in the database (1.3)
+
   
 
 Whatever means are chosen, the plugin simply passes all options to omniauth-saml. See [their configuration
 documentation](https://github.com/omniauth/omniauth-saml#usage) for further details.
 
-The three options are mutually exclusive. I.e. if settings are already provided via the `configuration.yml` file, settings in a `settings.yml` file will be ignored. Environment variables will override the `configuration.yml` based configuration, though.
-
+The options are mutually exclusive. I.e. if settings are already provided via ENV variables, settings in a `settings.yml` file will be ignored. If you decide to save settings in the database, they will override any ENV variables you might have set.
 
+#### 1.1 config/plugins/auth_saml/settings.yml file
 
-#### 1.1 configuration.yml file
+In your OpenProject packaged installation, you can modify the `/opt/openproject/config/plugins/auth_saml/settings.yml` file. This will contains the complete OpenProject configuration and can be extended to also contain metadata settings and connection details for your SSO identity provider.
 
-In your OpenProject packaged installation, you can modify the `/opt/openproject/config/configuration.yml` file. This will contains the complete OpenProject configuration and can be extended to also contain metadata settings and connection details for your SSO identity provider.
-
-Everything belonging to the `saml` key will be made available to the plugin. The first key below `saml` can be freely chosen (`my_saml` in the example).
+The following is an exemplary file with a set of common settings:
 
 ```yaml
-production:
-  # <-- other configuration -->
-
 saml:
-    my_saml:
   name: "saml"
   display_name: "My SSO"
   # Use the default SAML icon
@@ -77,11 +73,9 @@ production:
     first_name: ['givenName']
     # What attribute in SAML maps to the last name (default: sn)
     last_name: ['sn']
-
-  # <-- other configuration -->
 ```
 
-Be sure to choose the correct indentation and base key. The `saml` key should be indented two spaces (and all other keys accordingly) and the configuration should belong to the `production` group.
+Be sure to choose the correct indentation and base key. The items below the `saml` key should be indented two spaces. You will get an YAML parsing error otherwise when trying to start OpenProject.
 
 #### 1.2 Environment variables
 
@@ -116,13 +110,13 @@ That means it's best to set them using the console.
 > docker-compose run --rm web bundle exec rails console
 ```
 
-Once on the console you can set the same values as named in the `configuration.yml` file.
+Once on the console you can set the same values as named in the `settings.yml` file, however they need to be nested within a 'providers' key as follows.
 For example:
 
 ```ruby
 Setting.plugin_openproject_auth_saml = Hash(Setting.plugin_openproject_auth_saml).deep_merge({
   "providers" => {
-    "my_saml" => {
+    "saml" => {
       "name" => "saml",
       "display_name" => "My SSO",
       "assertion_consumer_service_url" => "https:/<YOUR OPENPROJECT HOSTNAME>/auth/saml/callback"