Sso deployment tutorial:

- reorder setup and start docker containers
- Added new section about deployment of sso
- added new variables related to servers deployment

Author: MarcelGeo

src/server/environment/index.md

@@ -152,4 +152,11 @@ Your webmaps won’t display the default background map unless we enable them on
 Alternatively, you can set up your own background map.
 :::
 
+## Single Sign-On (SSO)
+<ServerType type="EE" />
 
+| Variable name            | Type     | Default                       | Description                    |
+|--------------------------|----------|-------------------------------|--------------------------------|
+| `SSO_ENABLED`            | boolean  | `false`                       | Flag to enable SSO in Mergin Maps              |
+| `SSO_SERVER_URL`           | string   | `http://localhost:5225`     | Public URL of the SSO server. This URL should be accessible from the internet. |
+| `SSO_SERVER_API_KEY`      | string   | ``                      | API key used to authenticate requests to the SSO serice. |

src/server/install/index.md

@@ -46,15 +46,19 @@ cd deployment/community
 cd deployment/enterprise
 ```
 
-### Start docker containers
-
-Provided that `docker` and `docker-compose` are installed on your host, running <MainPlatformName /> stack should be as simple as running `docker-compose`. However, before doing that you would need to [configure](../environment/) your server setup via environment variables in `.prod.env` file.
-If you have not created this file yet, please do so from the provided `.env.template` file provided.
+### Setup environment
+​
+Now tweak deployment settings by modifying environment variables. You have to fix all variables marked as required in this list of [environment variables](../environment/). However, before doing that you would need to setup environment variables in `.prod.env` file.
+If you have not created this file yet, please do so from the provided `.env.template` file.
 
 ```shell
 cp .env.template .prod.env
 ```
 
+### Start docker containers
+
+Provided that `docker` and `docker-compose` are installed on your host, running <MainPlatformName /> stack should be as simple as running `docker-compose`.
+
 Once configured, you can run:
 ```shell
 # For community edition
@@ -85,11 +89,66 @@ $ docker exec merginmaps-server flask user create <username> <password> --is-adm
 ```
 :::
 
-### Setup environment
-​
-Now tweak deployment settings by modifying environment variables. You have to fix all variables marked as required in this list of [environment variables](../environment/). Some of the most common issues with custom deployments are listed in the [troubleshoot](../troubleshoot/) section.
+## Deployment of Single Sign On (SSO)
+<ServerType type="EE" />
+
+TTo enable SSO in <MainPlatformName />, ensure that you have the following environment variables set in your `.prod.env` file:
+
+```shell
+SSO_ENABLED=True
+SSO_SERVER_URL=<PUBLIC URL OF SSO SERVER>
+```
+
+The <MainPlatformName /> server is integrated with the most commonly used SAML and OIDC identity providers via the [Ory Polis](https://www.ory.sh/docs/polis) service. To run the Ory Polis stack, you need to provide environment variables in the `.sso.env` file. In the <GitHubRepo id="MerginMaps/server/blob/master/deployment/enterprise" desc="deployment folder for the enterprise edition" />, you can find the .sso.env.template file with all the required variables and their default values. Use the provided script to automatically pre-generate the `.sso.env` file with all the necessary variables.
+
+```shell
+cd deployment/enterprise/sso
+./sso-init.sh
+```
+
+The script will also pre-generate the `SSO_SERVER_API_KEY` variable the <MainPlatformName /> server. This variable is used to authenticate the <MainPlatformName /> server with Ory Polis. If you created the .sso.env file manually, you need to set this variable to match one of the `JACKSON_API_KEYS`.
+
+Pay close attention to these environment variables and change their default values: `NEXTAUTH_ADMIN_CREDENTIALS`, `RETRACED_ADMIN_ROOT_TOKEN`, `NEXTAUTH_ACL`. To set up your connection with a SAML application (e.g Google SAML or Entra), fill in the `SAML_AUDIENCE` variable with a domain name. More details [here](https://www.ory.sh/docs/polis/deploy/env-variables#saml_audience).
 
-### Test deployment
+:::tip Production deployment
+We recommend editing the `.sso.env` file manually and generating your own secrets and certificates for Ory Polis.
+:::
+
+If you want to configure the Ory Polis service to run on its own domain in production (e.g., `sso.example.com`), you need to add this domain to the following variables:
+
+* `EXTERNAL_URL=https://sso.example.com`
+* `NEXTAUTH_URL=https://sso.example.com`
+* `SSO_SERVER_URL=https://sso.example.com`
+
+:::tip <MainPlatformName /> and Ory Polis communication
+If your <MainPlatformName /> server is running without a connection to the publicly available Ory Polis `SSO_SERVER_URL`, you can set internal IP or domain names (e.g. `http://sso:5225`) in the following variables to ensure communication: `SSO_SERVER_INTERNAL_URL=http://sso:5225` and `SSO_SERVER_API_URL=http://sso:5225`.
+:::
+
+### Start the SSO stack
+
+To run the SSO stack, you need to have a running <MainPlatformName /> server - see previous section about [deployment](#deployment). 
+
+Mount the `deployment/enterprise/sso/sso-nginx.conf` file to the `merginmaps-proxy` container in the `docker-compose.yml` file:
+
+```yaml
+volumes:
+  - ./sso/sso-nginx.conf:/etc/nginx/templates/sso.conf.template
+```
+
+Then restart or reload the configuration in the `merginmaps-proxy` container and start the SSO stack:
+
+```shell
+docker compose -f docker-compose.sso.yml up -d
+```
+
+If you follow previous steps, the admin panel and authorization server for Ory Polis will be available at `http://localhost:8081`.
+
+:::tip Domain for SSO Service 
+We recommend running the Ory Polis server on a separate domain or subdomain to make it accessible to your users. The `deployment/enterprise/sso/sso-nginx.conf` file provides a reverse proxy configuration for running in a local environment. For your production deployment, use HTTPS to serve the SSO service. See the ssl-sso-nginx.conf file in the <GitHubRepo id="MerginMaps/server/blob/master/deployment/" desc="deployment folder" />. 
+:::
+
+
+## Test deployment
 
 In order to test your deployment there are some utility commands to perform basic checks.
 
@@ -128,3 +187,5 @@ By default, email notifications are disabled, so output will be similar to this:
 ```
 
 To enable them, set variable `MAIL_SUPPRESS_SEND` in accordance to above and fill all `MAIL_*` related variables with your company SMTP server configuration.
+
+Some of the most common issues with custom deployments are listed in the [troubleshoot](../troubleshoot/) section.