Migrate to Docusaurus (#329)

* docs: initial migration to docusaurus

* website: add custom font, update blurbs and icons

* website: update splash

* root: update links to docs

* flows: use .pbflow extension so docusaurus doesn't mangle the files

* e2e: workaround prospector

* Squashed commit of the following:

commit 1248585dca
Author: Jens Langhammer <jens.langhammer@beryju.org>
Date:   Sun Nov 15 20:46:53 2020 +0100

    e2e: attempt to fix prospector error again

commit 1319c480c4
Author: Jens Langhammer <jens.langhammer@beryju.org>
Date:   Sun Nov 15 20:41:35 2020 +0100

    ci: install previous python version for upgrade testing

* web: update accent colours and format

* website: format markdown files

* website: fix colours for text

* website: switch to temporary accent colour to improve readability

* flows: fix path for TestTransferDocs

* flows: fix formatting of tests

website/docs/expressions/index.md

@@ -0,0 +1,69 @@
+---
+title: Expressions
+---
+
+Expressions allow you to write custom logic using Python code.
+
+Expressions are used in different places throughout passbook, and can do different things.
+
+:::info
+These functions/objects are available wherever expressions are used. For more specific information, see [Expression Policies](../policies/expression.md) and [Property Mappings](../property-mappings/expression.md)
+:::
+
+## Global objects
+
+-   `pb_logger`: structlog BoundLogger. ([ref](https://www.structlog.org/en/stable/api.html#structlog.BoundLogger))
+-   `requests`: requests Session object. ([ref](https://requests.readthedocs.io/en/master/user/advanced/))
+
+## Generally available functions
+
+### `regex_match(value: Any, regex: str) -> bool`
+
+Check if `value` matches Regular Expression `regex`.
+
+Example:
+
+```python
+return regex_match(request.user.username, '.*admin.*')
+```
+
+### `regex_replace(value: Any, regex: str, repl: str) -> str`
+
+Replace anything matching `regex` within `value` with `repl` and return it.
+
+Example:
+
+```python
+user_email_local = regex_replace(request.user.email, '(.+)@.+', '')
+```
+
+### `pb_is_group_member(user: User, **group_filters) -> bool`
+
+Check if `user` is member of a group matching `**group_filters`.
+
+Example:
+
+```python
+return pb_is_group_member(request.user, name="test_group")
+```
+
+### `pb_user_by(**filters) -> Optional[User]`
+
+Fetch a user matching `**filters`. Returns "None" if no user was found.
+
+Example:
+
+```python
+other_user = pb_user_by(username="other_user")
+```
+
+## Comparing IP Addresses
+
+To compare IP Addresses or check if an IP Address is within a given subnet, you can use the functions `ip_address('192.0.2.1')` and `ip_network('192.0.2.0/24')`. With these objects you can do [arithmetic operations](https://docs.python.org/3/library/ipaddress.html#operators).
+
+You can also check if an IP Address is within a subnet by writing the following:
+
+```python
+ip_address('192.0.2.1') in ip_network('192.0.2.0/24')
+# evaluates to True
+```

website/docs/expressions/reference/user-object.md

@@ -0,0 +1,29 @@
+---
+title: User Object
+---
+
+The User object has the following attributes:
+
+-   `username`: User's username.
+-   `email` User's email.
+-   `name` User's display name.
+-   `is_staff` Boolean field if user is staff.
+-   `is_active` Boolean field if user is active.
+-   `date_joined` Date user joined/was created.
+-   `password_change_date` Date password was last changed.
+-   `attributes` Dynamic attributes.
+-   `group_attributes` Merged attributes of all groups the user is member of and the user's own attributes.
+-   `pb_groups` This is a queryset of all the user's groups.
+
+    You can do additional filtering like `user.pb_groups.filter(name__startswith='test')`, see [here](https://docs.djangoproject.com/en/3.1/ref/models/querysets/#id4)
+
+    To get the name of all groups, you can do `[group.name for group in user.pb_groups.all()]`
+
+## Examples
+
+List all the User's group names:
+
+```python
+for group in user.pb_groups.all():
+    yield group.name
+```

website/docs/flow/examples.md

@@ -0,0 +1,51 @@
+---
+title: Example Flows
+---
+
+:::info
+You can apply theses flows multiple times to stay updated, however this will discard all changes you've made.
+:::
+
+## Enrollment (2 Stage)
+
+Flow: right-click [here](/flows/enrollment-2-stage.pbflow) and save the file.
+
+Sign-up flow for new users, which prompts them for their username, email, password and name. No verification is done. Users are also immediately logged on after this flow.
+
+## Enrollment with email verification
+
+Flow: right-click [here](/flows/enrollment-email-verification.pbflow) and save the file.
+
+Same flow as above, with an extra email verification stage.
+
+You'll probably have to adjust the Email stage and set your connection details.
+
+## Two-factor Login
+
+Flow: right-click [here](/flows/login-2fa.pbflow) and save the file.
+
+Login flow which follows the default pattern (username/email, then password), but also checks for the user's OTP token, if they have one configured
+
+## Login with conditional Captcha
+
+Flow: right-click [here](/flows/login-conditional-captcha.pbflow) and save the file.
+
+Login flow which conditionally shows the users a captcha, based on the reputation of their IP and Username.
+
+By default, the captcha test keys are used. You can get a proper key [here](https://www.google.com/recaptcha/intro/v3.html)
+
+## Recovery with email verification
+
+Flow: right-click [here](/flows/recovery-email-verification.pbflow) and save the file.
+
+Recovery flow, the user is sent an email after they've identified themselves. After they click on the link in the email, they are prompted for a new password and immediately logged on.
+
+## User deletion
+
+Flow: right-click [here](/flows/unenrollment.pbflow) and save the file.
+
+Flow for users to delete their account,
+
+:::warning
+This is done without any warning.
+:::

website/docs/flow/flows.md

@@ -0,0 +1,46 @@
+---
+title: Flows
+---
+
+Flows are a method of describing a sequence of stages. A stage represents a single verification or logic step. They are used to authenticate users, enroll them, and more.
+
+Upon flow execution, a plan containing all stages is generated. This means that all attached policies are evaluated upon execution. This behaviour can be altered by enabling the **Re-evaluate Policies** option on the binding.
+
+To determine which flow is linked, passbook searches all flows with the required designation and chooses the first instance the current user has access to.
+
+## Permissions
+
+Flows can have policies assigned to them. These policies determine if the current user is allowed to see and use this flow.
+
+## Designation
+
+Flows are designated for a single purpose. This designation changes when a flow is used. The following designations are available:
+
+### Authentication
+
+This is designates a flow to be used for authentication.
+
+The authentication flow should always contain a [**User Login**](stages/user_login.md) stage, which attaches the staged user to the current session.
+
+### Invalidation
+
+This designates a flow to be used to invalidate a session.
+
+This stage should always contain a [**User Logout**](stages/user_logout.md) stage, which resets the current session.
+
+### Enrollment
+
+This designates a flow for enrollment. This flow can contain any amount of verification stages, such as [**email**](stages/email/index.md) or [**captcha**](stages/captcha/index.md). At the end, to create the user, you can use the [**user_write**](stages/user_write.md) stage, which either updates the currently staged user, or if none exists, creates a new one.
+
+### Unenrollment
+
+This designates a flow for unenrollment. This flow can contain any amount of verification stages, such as [**email**](stages/email/index.md) or [**captcha**](stages/captcha/index.md). As a final stage, to delete the account, use the [**user_delete**](stages/user_delete.md) stage.
+
+### Recovery
+
+This designates a flow for recovery. This flow normally contains an [**identification**](stages/identification/index.md) stage to find the user. It can also contain any amount of verification stages, such as [**email**](stages/email/index.md) or [**captcha**](stages/captcha/index.md).
+Afterwards, use the [**prompt**](stages/prompt/index.md) stage to ask the user for a new password and the [**user_write**](stages/user_write.md) stage to update the password.
+
+### Setup
+
+This designates a flow for general setup. This designation doesn't have any constraints in what you can do. For example, by default this designation is used to configure Factors, like change a password and setup TOTP.

website/docs/flow/stages/captcha/index.md

@@ -0,0 +1,9 @@
+---
+title: Captcha stage
+---
+
+This stage adds a form of verification using [Google's ReCaptcha](https://www.google.com/recaptcha/intro/v3.html).
+
+This stage has two required fields: Public key and private key. These can both be acquired at https://www.google.com/recaptcha/admin.
+
+![](captcha-admin.png)

website/docs/flow/stages/dummy/index.md

@@ -0,0 +1,7 @@
+---
+title: Dummy stage
+---
+
+This stage is used for development and has no function. It presents the user with a form which requires a single confirmation.
+
+![](dummy.png)

website/docs/flow/stages/email/index.md

@@ -0,0 +1,7 @@
+---
+title: Email stage
+---
+
+This stage can be used for email verification. passbook's background worker will send an email using the specified connection details. When an email can't be delivered, delivery is automatically retried periodically.
+
+![](email-recovery.png)

website/docs/flow/stages/identification/index.md

@@ -0,0 +1,27 @@
+---
+title: Identification stage
+---
+
+This stage provides a ready-to-go form for users to identify themselves.
+
+## Options
+
+### User Fields
+
+Select which fields the user can use to identify themselves. Multiple fields can be specified and separated with a comma.
+Valid choices:
+
+-   email
+-   username
+
+### Template
+
+This specifies which template is rendered. Currently there are two templates:
+
+The `Login` template shows configured Sources below the login form, as well as linking to the defined Enrollment and Recovery flows.
+
+The `Recovery` template shows only the form.
+
+### Enrollment/Recovery Flow
+
+These fields specify if and which flows are linked on the form. The enrollment flow is linked as `Need an account? Sign up.`, and the recovery flow is linked as `Forgot username or password?`.

website/docs/flow/stages/invitation/index.md

@@ -0,0 +1,9 @@
+---
+title: Invitation stage
+---
+
+This stage can be used to invite users. You can use this to enroll users with preset values.
+
+If the option `Continue Flow without Invitation` is enabled, this stage will continue even when no invitation token is present.
+
+To check if a user has used an invitation within a policy, you can check `request.context.invitation_in_effect`.

website/docs/flow/stages/otp_static/index.md

@@ -0,0 +1,7 @@
+---
+title: OTP Static stage
+---
+
+This stage configures static OTP Tokens, which can be used as a backup method to time-based OTP tokens.
+
+You can configure how many tokens are shown to the user.

website/docs/flow/stages/otp_time/index.md

@@ -0,0 +1,7 @@
+---
+title: OTP Time stage
+---
+
+This stage configures a time-based OTP Device, such as Google Authenticator or Authy.
+
+You can configure how many digest should be used for the OTP Token.

website/docs/flow/stages/otp_validation/index.md

@@ -0,0 +1,5 @@
+---
+title: OTP Validation stage
+---
+
+This stage validates an already configured OTP Device. This device has to be configured using an [OTP Time stage](../otp_time/index.md) or [OTP Static stage](../otp_static/index.md).

website/docs/flow/stages/password/index.md

@@ -0,0 +1,5 @@
+---
+title: Password stage
+---
+
+This is a generic password prompt which authenticates the current `pending_user`. This stage allows the selection of the source the user is authenticated against.

website/docs/flow/stages/prompt/index.md

@@ -0,0 +1,44 @@
+---
+title: Prompt stage
+---
+
+This stage is used to show the user arbitrary prompts.
+
+## Prompt
+
+The prompt can be any of the following types:
+
+| Type     | Description                                                       |
+| -------- | ----------------------------------------------------------------- |
+| text     | Arbitrary text. No client-side validation is done.                |
+| email    | Email input. Requires a valid email adress.                       |
+| password | Password input.                                                   |
+| number   | Number input. Any number is allowed.                              |
+| checkbox | Simple checkbox.                                                  |
+| hidden   | Hidden input field. Allows for the pre-setting of default values. |
+
+A prompt has the following attributes:
+
+### `field_key`
+
+The HTML name used for the prompt. This key is also used to later retrieve the data in expression policies:
+
+```python
+request.context.get('prompt_data').get('<field_key>')
+```
+
+### `label`
+
+The label used to describe the field. Depending on the selected template, this may not be shown.
+
+### `required`
+
+A flag which decides whether or not this field is required.
+
+### `placeholder`
+
+A field placeholder, shown within the input field. This field is also used by the `hidden` type as the actual value.
+
+### `order`
+
+The numerical index of the prompt. This applies to all stages which this prompt is a part of.

website/docs/flow/stages/prompt/validation.md

@@ -0,0 +1,19 @@
+---
+title: Prompt stage validation
+---
+
+Further validation of prompts can be done using policies.
+
+To validate that two password fields are identical, create the following expression policy:
+
+```python
+if request.context.get('prompt_data').get('password') == request.context.get('prompt_data').get('password_repeat'):
+    return True
+
+pb_message("Passwords don't match.")
+return False
+```
+
+This policy expects you to have two password fields with `field_key` set to `password` and `password_repeat`.
+
+Afterwards, bind this policy to the prompt stage you want to validate.

website/docs/flow/stages/user_delete.md

@@ -0,0 +1,11 @@
+---
+title: User delete stage
+---
+
+:::danger
+This stage deletes the `pending_user` without any confirmation. You have to make sure the user is aware of this.
+:::
+
+This stage is intended for an unenrollment flow. It deletes the currently pending user.
+
+The pending user is also removed from the current session.

website/docs/flow/stages/user_login.md

@@ -0,0 +1,7 @@
+---
+title: User login stage
+---
+
+This stage attaches a currently pending user to the current session.
+
+It can be used after `user_write` during an enrollment flow, or after a `password` stage during an authentication flow.

website/docs/flow/stages/user_logout.md

@@ -0,0 +1,5 @@
+---
+title: User logout stage
+---
+
+Opposite stage of [User Login Stages](user_login.md). It removes the user from the current session.

website/docs/flow/stages/user_write.md

@@ -0,0 +1,5 @@
+---
+title: User write stage
+---
+
+This stages writes data from the current context to the current pending user. If no user is pending, a new one is created.

website/docs/index.md

@@ -0,0 +1,17 @@
+---
+title: Welcome to passbook
+slug: /
+---
+
+## What is passbook?
+
+passbook is an open-source Identity Provider focused on flexibility and versatility. You can use passbook in an existing environment to add support for new protocols. passbook is also a great solution for implementing signup/recovery/etc in your application, so you don't have to deal with it.
+
+## Installation
+
+See [Docker-compose](installation/docker-compose.md) or [Kubernetes](installation/kubernetes.md)
+
+## Screenshots
+
+![](/img/screen_apps.png)
+![](/img/screen_admin.png)

website/docs/installation/docker-compose.md

@@ -0,0 +1,46 @@
+---
+title: docker-compose installation
+---
+
+This installation method is for test-setups and small-scale productive setups.
+
+## Prerequisites
+
+-   docker
+-   docker-compose
+
+## Install
+
+Download the latest `docker-compose.yml` from [here](https://raw.githubusercontent.com/BeryJu/passbook/master/docker-compose.yml). Place it in a directory of your choice.
+
+To optionally enable error-reporting, run `echo PASSBOOK_ERROR_REPORTING__ENABLED=true >> .env`
+
+To optionally deploy a different version run `echo PASSBOOK_TAG=0.12.10-stable >> .env`
+
+If this is a fresh passbook install run the following commands to generate a password:
+
+```
+sudo apt-get install -y pwgen
+echo "PG_PASS=$(pwgen 40 1)" >> .env
+echo "PASSBOOK_SECRET_KEY=$(pwgen 50 1)" >> .env
+```
+
+Afterwards, run these commands to finish
+
+```
+docker-compose pull
+docker-compose up -d
+docker-compose run --rm server migrate
+```
+
+The compose file statically references the latest version available at the time of downloading, which can be overridden with the `SERVER_TAG` environment variable.
+
+If you plan to use this setup for production, it is also advised to change the PostgreSQL password by setting `PG_PASS` to a password of your choice.
+
+Now you can pull the Docker images needed by running `docker-compose pull`. After this has finished, run `docker-compose up -d` to start passbook.
+
+passbook will then be reachable via HTTP on port 80, and HTTPS on port 443. You can optionally configure the packaged traefik to use Let's Encrypt certificates for TLS Encryption.
+
+If you plan to access passbook via a reverse proxy which does SSL Termination, make sure you use the HTTPS port, so passbook is aware of the SSL connection.
+
+The initial setup process also creates a default admin user, the username and password for which is `pbadmin`. It is highly recommended to change this password as soon as you log in.

website/docs/installation/index.md

@@ -0,0 +1,7 @@
+---
+title: Installation
+---
+
+If you want to try out passbook, or only want a small deployment (< 100 Users), you should use [docker-compose](./docker-compose).
+
+If you want a larger deployment, or you want High-Availability, you should use [Kubernetes](./kubernetes).

website/docs/installation/kubernetes.md

@@ -0,0 +1,76 @@
+---
+title: Kubernetes installation
+---
+
+For a mid to high-load installation, Kubernetes is recommended. passbook is installed using a helm-chart.
+
+This installation automatically applies database migrations on startup. After the installation is done, you can use `pbadmin` as username and password.
+
+```yaml
+###################################
+# Values directly affecting passbook
+###################################
+image:
+    name: beryju/passbook
+    name_static: beryju/passbook-static
+    tag: 0.12.10-stable
+
+serverReplicas: 1
+workerReplicas: 1
+
+# Enable the Kubernetes integration which lets passbook deploy outposts into kubernetes
+kubernetesIntegration: true
+
+config:
+    # Optionally specify fixed secret_key, otherwise generated automatically
+    # secretKey: _k*@6h2u2@q-dku57hhgzb7tnx*ba9wodcb^s9g0j59@=y(@_o
+    # Enable error reporting
+    errorReporting:
+        enabled: false
+        environment: customer
+        sendPii: false
+    # Log level used by web and worker
+    # Can be either debug, info, warning, error
+    logLevel: warning
+
+# Enable Database Backups to S3
+# backup:
+#   accessKey: access-key
+#   secretKey: secret-key
+#   bucket: s3-bucket
+#   region: eu-central-1
+#   host: s3-host
+
+ingress:
+    annotations:
+        {}
+        # kubernetes.io/ingress.class: nginx
+        # kubernetes.io/tls-acme: "true"
+    hosts:
+        - passbook.k8s.local
+    tls: []
+    #  - secretName: chart-example-tls
+    #    hosts:
+    #      - passbook.k8s.local
+
+###################################
+# Values controlling dependencies
+###################################
+
+install:
+    postgresql: true
+    redis: true
+
+# These values influence the bundled postgresql and redis charts, but are also used by passbook to connect
+postgresql:
+    postgresqlDatabase: passbook
+
+redis:
+    cluster:
+        enabled: false
+    master:
+        persistence:
+            enabled: false
+        # https://stackoverflow.com/a/59189742
+        disableCommands: []
+```

website/docs/installation/reverse-proxy.md

@@ -0,0 +1,45 @@
+---
+title: passbook behind a reverse-proxy
+---
+
+If you want to access passbook behind a reverse-proxy, use a config like this. It is important that Websocket is enabled, so that Outposts can connect.
+
+```
+map $http_upgrade $connection_upgrade {
+    default upgrade;
+    ''      close;
+}
+
+server {
+    # Server config
+    listen 80;
+    server_name sso.domain.tld;
+
+    # 301 to SSL
+    location / {
+            return 301 https://$host$request_uri;
+    }
+}
+server {
+    # Server config
+    listen 443 ssl http2;
+    server_name sso.domain.tld;
+
+    # SSL Certs
+    ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem;
+    ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem;
+
+    # Proxy site
+    location / {
+        proxy_pass https://<hostname of your passbook server>;
+        proxy_http_version 1.1;
+        proxy_set_header X-Forwarded-Proto https;
+        proxy_set_header X-Forwarded-Port 443;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        # This needs to be set inside the location block, very important.
+        proxy_set_header Host $host;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection $connection_upgrade;
+    }
+}
+```

website/docs/integrations/services/aws/index.md

@@ -0,0 +1,75 @@
+---
+title: Amazon Web Services
+---
+
+## What is AWS
+
+:::note
+Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform, offering over 175 fully featured services from data centers globally. Millions of customers—including the fastest-growing startups, largest enterprises, and leading government agencies—are using AWS to lower costs, become more agile, and innovate faster.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `passbook.company` is the FQDN of the passbook install.
+
+Create an application in passbook and note the slug, as this will be used later. Create a SAML provider with the following parameters:
+
+-   ACS URL: `https://signin.aws.amazon.com/saml`
+-   Audience: `urn:amazon:webservices`
+-   Issuer: `passbook`
+-   Binding: `Post`
+
+You can of course use a custom signing certificate, and adjust durations.
+
+## AWS
+
+Create a role with the permissions you desire, and note the ARN.
+
+After you've created the Property Mappings below, add them to the Provider.
+
+Create an application, assign policies, and assign this provider.
+
+Export the metadata from passbook, and create an Identity Provider [here](https://console.aws.amazon.com/iam/home#/providers).
+
+#### Role Mapping
+
+The Role mapping specifies the AWS ARN(s) of the identity provider, and the role the user should assume ([see](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_saml_assertions.html#saml_role-attribute)).
+
+This Mapping needs to have the SAML Name field set to "https://aws.amazon.com/SAML/Attributes/Role"
+
+As expression, you can return a static ARN like so
+
+```python
+return "arn:aws:iam::123412341234:role/saml_role,arn:aws:iam::123412341234:saml-provider/passbook"
+```
+
+Or, if you want to assign AWS Roles based on Group membership, you can add a custom attribute to the Groups, for example "aws_role", and use this snippet below. Groups are sorted by name and later groups overwrite earlier groups' attributes.
+
+```python
+role_name = user.group_attributes().get("aws_role", "")
+return f"arn:aws:iam::123412341234:role/{role_name},arn:aws:iam::123412341234:saml-provider/passbook"
+```
+
+If you want to allow a user to choose from multiple roles, use this snippet
+
+```python
+return [
+    "arn:aws:iam::123412341234:role/role_a,arn:aws:iam::123412341234:saml-provider/passbook",
+    "arn:aws:iam::123412341234:role/role_b,arn:aws:iam::123412341234:saml-provider/passbook",
+    "arn:aws:iam::123412341234:role/role_c,arn:aws:iam::123412341234:saml-provider/passbook",
+]
+```
+
+### RoleSessionName Mapping
+
+The RoleSessionMapping specifies what identifier will be shown at the top of the Management Console ([see](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_saml_assertions.html#saml_role-session-attribute)).
+
+This mapping needs to have the SAML Name field set to "https://aws.amazon.com/SAML/Attributes/RoleSessionName".
+
+To use the user's username, use this snippet
+
+```python
+return user.username
+```

website/docs/integrations/services/gitlab/index.md

@@ -0,0 +1,62 @@
+---
+title: GitLab
+---
+
+## What is GitLab
+
+From https://about.gitlab.com/what-is-gitlab/
+
+:::note
+GitLab is a complete DevOps platform, delivered as a single application. This makes GitLab unique and makes Concurrent DevOps possible, unlocking your organization from the constraints of a pieced together toolchain. Join us for a live Q&A to learn how GitLab can give you unmatched visibility and higher levels of efficiency in a single application across the DevOps lifecycle.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `gitlab.company` is the FQDN of the GitLab Install
+-   `passbook.company` is the FQDN of the passbook Install
+
+Create an application in passbook and note the slug, as this will be used later. Create a SAML provider with the following parameters:
+
+-   ACS URL: `https://gitlab.company/users/auth/saml/callback`
+-   Audience: `https://gitlab.company`
+-   Issuer: `https://gitlab.company`
+-   Binding: `Post`
+
+You can of course use a custom signing certificate, and adjust durations. To get the value for `idp_cert_fingerprint`, you can use a tool like [this](https://www.samltool.com/fingerprint.php).
+
+## GitLab Configuration
+
+Paste the following block in your `gitlab.rb` file, after replacing the placeholder values from above. The file is located in `/etc/gitlab`.
+
+```ruby
+gitlab_rails['omniauth_enabled'] = true
+gitlab_rails['omniauth_allow_single_sign_on'] = ['saml']
+gitlab_rails['omniauth_sync_email_from_provider'] = 'saml'
+gitlab_rails['omniauth_sync_profile_from_provider'] = ['saml']
+gitlab_rails['omniauth_sync_profile_attributes'] = ['email']
+gitlab_rails['omniauth_auto_sign_in_with_provider'] = 'saml'
+gitlab_rails['omniauth_block_auto_created_users'] = false
+gitlab_rails['omniauth_auto_link_saml_user'] = true
+gitlab_rails['omniauth_providers'] = [
+  {
+    name: 'saml',
+    args: {
+      assertion_consumer_service_url: 'https://gitlab.company/users/auth/saml/callback',
+      idp_cert_fingerprint: '4E:1E:CD:67:4A:67:5A:E9:6A:D0:3C:E6:DD:7A:F2:44:2E:76:00:6A',
+      idp_sso_target_url: 'https://passbook.company/application/saml/<passbook application slug>/sso/binding/post/',
+      issuer: 'https://gitlab.company',
+      name_identifier_format: 'urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress',
+      attribute_statements: {
+        email: ['urn:oid:1.3.6.1.4.1.5923.1.1.1.6'],
+        first_name: ['urn:oid:2.5.4.3'],
+        nickname: ['urn:oid:2.16.840.1.113730.3.1.241']
+      }
+    },
+    label: 'passbook'
+  }
+]
+```
+
+Afterwards, either run `gitlab-ctl reconfigure` if you're running GitLab Omnibus, or restart the container if you're using the container.

website/docs/integrations/services/harbor/index.md

@@ -0,0 +1,30 @@
+---
+title: Harbor
+---
+
+## What is Harbor
+
+From https://goharbor.io
+
+:::note
+Harbor is an open source container image registry that secures images with role-based access control, scans images for vulnerabilities, and signs images as trusted. A CNCF Incubating project, Harbor delivers compliance, performance, and interoperability to help you consistently and securely manage images across cloud native compute platforms like Kubernetes and Docker.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `harbor.company` is the FQDN of the Harbor install.
+-   `passbook.company` is the FQDN of the passbook install.
+
+Create an application in passbook. Create an OpenID provider with the following parameters:
+
+-   Client Type: `Confidential`
+-   Response types: `code (Authorization Code Flow)`
+-   JWT Algorithm: `RS256`
+-   Redirect URIs: `https://harbor.company/c/oidc/callback`
+-   Scopes: `openid`
+
+## Harbor
+
+![](./harbor.png)

website/docs/integrations/services/home-assistant/index.md

@@ -0,0 +1,61 @@
+---
+title: Home-Assistant
+---
+
+## What is Home-Assistant
+
+From https://www.home-assistant.io/
+
+:::note
+Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `hass.company` is the FQDN of the Home-Assistant install.
+-   `passbook.company` is the FQDN of the passbook install.
+
+:::note
+This setup uses https://github.com/BeryJu/hass-auth-header and the passbook proxy for authentication. When this [PR](https://github.com/home-assistant/core/pull/32926) is merged, this will no longer be necessary.
+:::
+
+## Home-Assistant
+
+This guide requires https://github.com/BeryJu/hass-auth-header, which can be installed as described in the Readme.
+
+Afterwards, make sure the `trusted_proxies` setting contains the IP(s) of the Host(s) passbook is running on.
+
+With the default Header of `X-Forwarded-Preferred-Username` matching is done on a username basis, so your Name in Home-Assistant and your username in passbook have to match.
+
+If this is not the case, you can simply add an additional header for your user, which contains the Home-Assistant Name and authenticate based on that.
+
+For example add this to your user's properties and set the Header to `X-pb-hass-user`.
+
+```yaml
+additionalHeaders:
+    X-pb-hass-user: some other name
+```
+
+## passbook
+
+Create a Proxy Provider with the following values
+
+-   Internal host
+
+    If Home-Assistant is running in docker, and you're deploying the passbook proxy on the same host, set the value to `http://homeassistant:8123`, where Home-Assistant is the name of your container.
+
+    If Home-Assistant is running on a different server than where you are deploying the passbook proxy, set the value to `http://hass.company:8123`.
+
+-   External host
+
+    Set this to the external URL you will be accessing Home-Assistant from.
+
+Create an application in passbook and select the provider you've created above.
+
+## Deployment
+
+Create an outpost deployment for the provider you've created above, as described [here](../../../outposts/outposts.md). Deploy this Outpost either on the same host or a different host that can access Home-Assistant.
+
+The outpost will connect to passbook and configure itself.

website/docs/integrations/services/rancher/index.md

@@ -0,0 +1,31 @@
+---
+title: Rancher
+---
+
+## What is Rancher
+
+From https://rancher.com/products/rancher
+
+:::note
+An enterprise platform for managing Kubernetes Everywhere
+Rancher is a platform built to address the needs of the DevOps teams deploying applications with Kubernetes, and the IT staff responsible for delivering an enterprise-critical service.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `rancher.company` is the FQDN of the Rancher install.
+-   `passbook.company` is the FQDN of the passbook install.
+
+Create an application in passbook and note the slug, as this will be used later. Create a SAML provider with the following parameters:
+
+-   ACS URL: `https://rancher.company/v1-saml/adfs/saml/acs`
+-   Audience: `https://rancher.company/v1-saml/adfs/saml/metadata`
+-   Issuer: `passbook`
+
+You can of course use a custom signing certificate, and adjust durations.
+
+## Rancher
+
+![](./rancher.png)

website/docs/integrations/services/sentry/index.md

@@ -0,0 +1,48 @@
+---
+title: Sentry
+---
+
+## What is Sentry
+
+From https://sentry.io
+
+:::note
+Sentry provides self-hosted and cloud-based error monitoring that helps all software
+teams discover, triage, and prioritize errors in real-time.
+
+One million developers at over fifty thousand companies already ship
+better software faster with Sentry. Won’t you join them?
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `sentry.company` is the FQDN of the Sentry install.
+-   `passbook.company` is the FQDN of the passbook install.
+
+Create an application in passbook. Create a SAML Provider with the following values
+
+-   ACS URL: `https://sentry.company/saml/acs/<sentry organisation name>/`
+-   Audience: `https://sentry.company/saml/metadata/<sentry organisation name>/`
+-   Issuer: `passbook`
+-   Service Provider Binding: `Post`
+-   Property Mapping: Select all Autogenerated Mappings
+
+## Sentry
+
+**This guide assumes you've installed Sentry using [getsentry/onpremise](https://github.com/getsentry/onpremise)**
+
+Navigate to Settings -> Auth, and click on Configure next to SAML2
+
+![](./auth.png)
+
+In passbook, get the Metadata URL by right-clicking `Download Metadata` and selecting Copy Link Address, and paste that URL into Sentry.
+
+On the next screen, input these Values
+
+IdP User ID: `urn:oid:0.9.2342.19200300.100.1.1`
+User Email: `urn:oid:0.9.2342.19200300.100.1.3`
+First Name: `urn:oid:2.5.4.3`
+
+After confirming, Sentry will authenticate with passbook, and you should be redirected back to a page confirming your settings.

website/docs/integrations/services/sonarr/index.md

@@ -0,0 +1,44 @@
+---
+title: Sonarr
+---
+
+# Sonarr Integration
+
+:::note
+These instructions apply to all projects in the \*arr Family. If you use multiple of these projects, you can assign them to the same Outpost.
+:::
+
+## What is Sonarr
+
+From https://github.com/Sonarr/Sonarr
+
+:::note
+Sonarr is a PVR for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new episodes of your favorite shows and will grab, sort and rename them. It can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `sonarr.company` is the FQDN of the Sonarr install.
+-   `passbook.company` is the FQDN of the passbook install.
+
+Create a Proxy Provider with the following values
+
+-   Internal host
+
+    If Sonarr is running in docker, and you're deploying the passbook proxy on the same host, set the value to `http://sonarr:8989`, where sonarr is the name of your container.
+
+    If Sonarr is running on a different server than where you are deploying the passbook proxy, set the value to `http://sonarr.company:8989`.
+
+-   External host
+
+    Set this to the external URL you will be accessing Sonarr from.
+
+Create an application in passbook and select the provider you've created above.
+
+## Deployment
+
+Create an outpost deployment for the provider you've created above, as described [here](../../../outposts/outposts.md). Deploy this Outpost either on the same host or a different host that can access Sonarr.
+
+The outpost will connect to passbook and configure itself.

website/docs/integrations/services/tautulli/index.md

@@ -0,0 +1,53 @@
+---
+title: Tautulli
+---
+
+## What is Tautulli
+
+From https://tautulli.com/
+
+:::note
+Tautulli is a 3rd party application that you can run alongside your Plex Media Server to monitor activity and track various statistics. Most importantly, these statistics include what has been watched, who watched it, when and where they watched it, and how it was watched. The only thing missing is "why they watched it", but who am I to question your 42 plays of Frozen. All statistics are presented in a nice and clean interface with many tables and graphs, which makes it easy to brag about your server to everyone else.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `tautulli.company` is the FQDN of the Tautulli install.
+-   `passbook.company` is the FQDN of the passbook install.
+
+## passbook Setup
+
+Because Tautulli requires valid HTTP Basic credentials, you must save your HTTP Basic Credentials in passbook. The recommended way to do this is to create a Group. Name the group "Tautulli Users", for example. For this group, add the following attributes:
+
+```yaml
+tautulli_user: username
+tautulli_password: password
+```
+
+Add all Tautulli users to the Group. You should also create a Group Membership Policy to limit access to the application.
+
+Create an application in passbook. Create a Proxy provider with the following parameters:
+
+-   Internal host
+
+    If Tautulli is running in docker, and you're deploying the passbook proxy on the same host, set the value to `http://tautulli:3579`, where tautulli is the name of your container.
+
+    If Tautulli is running on a different server to where you are deploying the passbook proxy, set the value to `http://tautulli.company:3579`.
+
+-   External host
+
+    Set this to the external URL you will be accessing Tautulli from.
+
+Enable the `Set HTTP-Basic Authentication` option. Set and `HTTP-Basic Username` and `HTTP-Basic Password` to `tautulli_user` and `tautulli_password` respectively. These values can be chosen freely, `tautulli_` is just used as a prefix for clarity.
+
+## Tautulli Setup
+
+In Tautulli, navigate to Settings and enable the "Show Advanced" option. Navigate to "Web Interface" on the sidebar, and ensure the Option `Use Basic Authentication` is checked.
+
+![](./tautulli.png)
+
+Save the settings, and restart Tautulli if prompted.
+
+Afterwards, you need to deploy an Outpost in front of Tautulli, as descried [here](../sonarr/index.md)

website/docs/integrations/services/tower-awx/index.md

@@ -0,0 +1,79 @@
+---
+title: Ansible Tower / AWX
+---
+
+## What is Tower
+
+From https://docs.ansible.com/ansible/2.5/reference_appendices/tower.html
+
+:::note
+Ansible Tower (formerly ‘AWX’) is a web-based solution that makes Ansible even more easy to use for IT teams of all kinds. It’s designed to be the hub for all of your automation tasks.
+
+Tower allows you to control access to who can access what, even allowing sharing of SSH credentials without someone being able to transfer those credentials. Inventory can be graphically managed or synced with a wide variety of cloud sources. It logs all of your jobs, integrates well with LDAP, and has an amazing browsable REST API. Command line tools are available for easy integration with Jenkins as well. Provisioning callbacks provide great support for autoscaling topologies.
+:::
+
+:::note
+AWX is the open-source version of Tower. The term "AWX" will be used interchangeably throughout this document.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `awx.company` is the FQDN of the AWX/Tower install.
+-   `passbook.company` is the FQDN of the passbook install.
+
+Create an application in passbook and note the slug, as this will be used later. Create a SAML provider with the following parameters:
+
+-   ACS URL: `https://awx.company/sso/complete/saml/`
+-   Audience: `awx`
+-   Service Provider Binding: Post
+-   Issuer: `https://awx.company/sso/metadata/saml/`
+
+You can of course use a custom signing certificate, and adjust durations.
+
+## AWX Configuration
+
+Navigate to `https://awx.company/#/settings/auth` to configure SAML. Set the Field `SAML SERVICE PROVIDER ENTITY ID` to `awx`.
+
+For the fields `SAML SERVICE PROVIDER PUBLIC CERTIFICATE` and `SAML SERVICE PROVIDER PRIVATE KEY`, you can either use custom certificates, or use the self-signed pair generated by passbook.
+
+Provide metadata in the `SAML Service Provider Organization Info` field:
+
+```json
+{
+    "en-US": {
+        "name": "passbook",
+        "url": "https://passbook.company",
+        "displayname": "passbook"
+    }
+}
+```
+
+Provide metadata in the `SAML Service Provider Technical Contact` and `SAML Service Provider Technical Contact` fields:
+
+```json
+{
+    "givenName": "Admin Name",
+    "emailAddress": "admin@company"
+}
+```
+
+In the `SAML Enabled Identity Providers` paste the following configuration:
+
+```json
+{
+    "passbook": {
+        "attr_username": "urn:oid:2.16.840.1.113730.3.1.241",
+        "attr_user_permanent_id": "urn:oid:0.9.2342.19200300.100.1.1",
+        "x509cert": "MIIDEjCCAfqgAwIBAgIRAJZ9pOZ1g0xjiHtQAAejsMEwDQYJKoZIhvcNAQELBQAwMDEuMCwGA1UEAwwlcGFzc2Jvb2sgU2VsZi1zaWduZWQgU0FNTCBDZXJ0aWZpY2F0ZTAeFw0xOTEyMjYyMDEwNDFaFw0yMDEyMjYyMDEwNDFaMFkxLjAsBgNVBAMMJXBhc3Nib29rIFNlbGYtc2lnbmVkIFNBTUwgQ2VydGlmaWNhdGUxETAPBgNVBAoMCHBhc3Nib29rMRQwEgYDVQQLDAtTZWxmLXNpZ25lZDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAO/ktBYZkY9xAijF4acvzX6Q1K8KoIZeyde8fVgcWBz4L5FgDQ4/dni4k2YAcPdwteGL4nKVzetUzjbRCBUNuO6lqU4J4WNNX4Xg4Ir7XLRoAQeo+omTPBdpJ1p02HjtN5jT01umN3bK2yto1e37CJhK6WJiaXqRewPxh4lI4aqdj3BhFkJ3I3r2qxaWOAXQ6X7fg3w/ny7QP53//ouZo7hSLY3GIcRKgvdjjVM3OW5C3WLpOq5Dez5GWVJ17aeFCfGQ8bwFKde6qfYqyGcU9xHB36TtVHB9hSFP/tUFhkiSOxtsrYwCgCyXm4UTSpP+wiNyjKfFw7qGLBvA2hGTNw8CAwEAATANBgkqhkiG9w0BAQsFAAOCAQEAh9PeAqPRQk1/SSygIFADZBi08O/DPCshFwEHvJATIcTzcDD8UGAjXh+H5OlkDyX7KyrcaNvYaafCUo63A+WprdtdY5Ty6SBEwTYyiQyQfwM9BfK+imCoif1Ai7xAelD7p9lNazWq7JU+H/Ep7U7Q7LvpxAbK0JArt+IWTb2NcMb3OWE1r0gFbs44O1l6W9UbJTbyLMzbGbe5i+NHlgnwPwuhtRMh0NUYabGHKcHbhwyFhfGAQv2dAp5KF1E5gu6ZzCiFePzc0FrqXQyb2zpFYcJHXquiqaOeG7cZxRHYcjrl10Vxzki64XVA9BpdELgKSnupDGUEJsRUt3WVOmvZuA==",
+        "url": "https://passbook.company/application/saml/awx/login/",
+        "attr_last_name": "User.LastName",
+        "entity_id": "https://awx.company/sso/metadata/saml/",
+        "attr_email": "urn:oid:0.9.2342.19200300.100.1.3",
+        "attr_first_name": "urn:oid:2.5.4.3"
+    }
+}
+```
+
+`x509cert` is the certificate configured in passbook. Remove the `--BEGIN CERTIFICATE--` and `--END CERTIFICATE--` headers, then enter the cert as one non-breaking string.

website/docs/integrations/services/ubuntu-landscape/index.md

@@ -0,0 +1,60 @@
+---
+title: Ubuntu Landscape
+---
+
+## What is Ubuntu Landscape
+
+From https://en.wikipedia.org/wiki/Landscape_(software)
+
+:::note
+Landscape is a systems management tool developed by Canonical. It can be run on-premises or in the cloud depending on the needs of the user. It is primarily designed for use with Ubuntu derivatives such as Desktop, Server, and Core.
+:::
+
+:::warning
+This requires passbook 0.10.3 or newer.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `landscape.company` is the FQDN of the Landscape server.
+-   `passbook.company` is the FQDN of the passbook install.
+
+Landscape uses the OpenID-Connect Protocol for single-sign on.
+
+## passbook Setup
+
+Create an OAuth2/OpenID-Connect Provider with the default settings. Set the Redirect URIs to `https://landscape.company/login/handle-openid`. Select all Autogenerated Scopes.
+
+Keep Note of the Client ID and the Client Secret.
+
+Create an application and assign access policies to the application. Set the application's provider to the provider you've just created.
+
+## Landscape Setup
+
+On the Landscape Server, edit the file `/etc/landscape/service.conf` and add the following snippet under the `[landscape]` section:
+
+```
+oidc-issuer = https://passbook.company/application/o/<slug of the application you've created>/
+oidc-client-id = <client ID of the provider you've created>
+oidc-client-secret = <client Secret of the provider you've created>
+```
+
+Afterwards, run `sudo lsctl restart` to restart the Landscape services.
+
+## Appendix
+
+To make an OpenID-Connect User admin, you have to insert some rows into the database.
+
+First login with your passbook user, and make sure the user is created successfully.
+
+Run `sudo -u postgres psql landscape-standalone-main` on the Landscape server to open a PostgreSQL Prompt.
+Then run `select * from person;` to get a list of all users. Take note of the ID given to your new user.
+
+Run the following commands to make this user an administrator:
+
+```sql
+INSERT INTO person_account VALUES (<user id>, 1);
+INSERT INTO person_access VALUES (<user id>, 1, 1);
+```

website/docs/integrations/services/vmware-vcenter/index.md

@@ -0,0 +1,86 @@
+---
+title: VMware vCenter
+---
+
+## What is vCenter
+
+From https://en.wikipedia.org/wiki/VCenter
+
+:::note
+vCenter Server is the centralized management utility for VMware, and is used to manage virtual machines, multiple ESXi hosts, and all dependent components from a single centralized location. VMware vMotion and svMotion require the use of vCenter and ESXi hosts.
+:::
+
+:::warning
+This requires passbook 0.10.3 or newer.
+:::
+
+:::warning
+This requires VMware vCenter 7.0.0 or newer.
+:::
+
+:::note
+It seems that the vCenter still needs to be joined to the Active Directory Domain, otherwise group membership does not work correctly. We're working on a fix for this, for the meantime your vCenter should be part of your Domain.
+:::
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `vcenter.company` is the FQDN of the vCenter server.
+-   `passbook.company` is the FQDN of the passbook install.
+
+Since vCenter only allows OpenID-Connect in combination with Active Directory, it is recommended to have passbook sync with the same Active Directory.
+
+### Step 1
+
+Under _Property Mappings_, create a _Scope Mapping_. Give it a name like "OIDC-Scope-VMware-vCenter". Set the scope name to `openid` and the expression to the following
+
+```python
+return {
+  "domain": "<your active directory domain>",
+}
+```
+
+### Step 2
+
+:::note
+If your Active Directory Schema is the same as your Email address schema, skip to Step 3.
+:::
+
+Under _Sources_, click _Edit_ and ensure that "Autogenerated Active Directory Mapping: userPrincipalName -> attributes.upn" has been added to your source.
+
+### Step 3
+
+Under _Providers_, create an OAuth2/OpenID Provider with these settings:
+
+-   Client Type: Confidential
+-   Response Type: code (ADFS Compatibility Mode, sends id_token as access_token)
+-   JWT Algorithm: RS256
+-   Redirect URI: `https://vcenter.company/ui/login/oauth2/authcode`
+-   Post Logout Redirect URIs: `https://vcenter.company/ui/login`
+-   Sub Mode: If your Email address Schema matches your UPN, select "Based on the User's Email...", otherwise select "Based on the User's UPN...".
+-   Scopes: Select the Scope Mapping you've created in Step 1
+
+![](./passbook_setup.png)
+
+### Step 4
+
+Create an application which uses this provider. Optionally apply access restrictions to the application.
+
+Set the Launch URL to `https://vcenter.company/ui/login/oauth2`. This will skip vCenter's User Prompt and directly log you in.
+
+## vCenter Setup
+
+Login as local Administrator account (most likely ends with vsphere.local). Using the Menu in the Navigation bar, navigate to _Administration -> Single Sing-on -> Configuration_.
+
+Click on _Change Identity Provider_ in the top-right corner.
+
+In the wizard, select "Microsoft ADFS" and click Next.
+
+Fill in the Client Identifier and Shared Secret from the Provider in passbook. For the OpenID Address, click on _View Setup URLs_ in passbook, and copy the OpenID Configuration URL.
+
+On the next page, fill in your Active Directory Connection Details. These should be similar to what you have set in passbook.
+
+![](./vcenter_post_setup.png)
+
+If your vCenter was already setup with LDAP beforehand, your Role assignments will continue to work.

website/docs/integrations/sources/active-directory/index.md

@@ -0,0 +1,57 @@
+---
+title: Active Directory
+---
+
+## Preparation
+
+The following placeholders will be used:
+
+-   `ad.company` is the Name of the Active Directory domain.
+-   `passbook.company` is the FQDN of the passbook install.
+
+## Active Directory Setup
+
+1. Open Active Directory Users and Computers
+
+2. Create a user in Active Directory, matching your naming scheme
+
+    ![](./01_user_create.png)
+
+3. Give the User a password, generated using for example `pwgen 64 1`.
+
+4. Open the Delegation of Control Wizard by right-clicking the domain.
+
+5. Select the passbook service user you've just created.
+
+6. Ensure the "Reset user password and force password change at next logon" Option is checked.
+
+    ![](./02_delegate.png)
+
+## passbook Setup
+
+In passbook, create a new LDAP Source in Administration -> Sources.
+
+Use these settings:
+
+-   Server URI: `ldap://ad.company`
+
+    For passbook to be able to write passwords back to Active Directory, make sure to use `ldaps://`
+
+-   Bind CN: `<name of your service user>@ad.company`
+-   Bind Password: The password you've given the user above
+-   Base DN: The base DN which you want passbook to sync
+-   Property Mappings: Select all and click the right arrow
+
+The other settings might need to be adjusted based on the setup of your domain.
+
+-   Addition User/Group DN: Additional DN which is _prepended_ to your Base DN for user synchronization.
+-   Addition Group DN: Additional DN which is _prepended_ to your Base DN for group synchronization.
+-   User object filter: Which objects should be considered users.
+-   Group object filter: Which objects should be considered groups.
+-   User group membership field: Which user field saves the group membership
+-   Object uniqueness field: A user field which contains a unique Identifier
+-   Sync parent group: If enabled, all synchronized groups will be given this group as a parent.
+
+After you save the source, a synchronization will start in the background. When its done, you cen see the summary on the System Tasks page.
+
+![](./03_pb_status.png)

website/docs/maintenance/backups/index.md

@@ -0,0 +1,103 @@
+---
+title: Backup and restore
+---
+
+:::warning
+Local backups are only supported for docker-compose installs. If you want to backup a Kubernetes instance locally, use an S3-compatible server such as [minio](https://min.io/)
+:::
+
+### Backup
+
+:::note
+Local backups are **enabled** by default, and will be run daily at 00:00
+:::
+
+Local backups can be created by running the following command in your passbook installation directory
+
+```
+docker-compose run --rm worker backup
+```
+
+This will dump the current database into the `./backups` folder. By defaults, the last 10 Backups are kept.
+
+### Restore
+
+Run this command in your passbook installation directory
+
+```
+docker-compose run --rm worker restore
+```
+
+This will prompt you to restore from your last backup. If you want to restore from a specific file, use the `-i` flag with the filename:
+
+```
+docker-compose run --rm worker restore -i default-2020-10-03-115557.psql
+```
+
+After you've restored the backup, it is recommended to restart all services with `docker-compose restart`.
+
+### S3 Configuration
+
+#### Preparation
+
+passbook expects the bucket you select to already exist. The IAM User given to passbook should have the following permissions
+
+```json
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Sid": "VisualEditor0",
+            "Effect": "Allow",
+            "Action": [
+                "s3:PutObject",
+                "s3:GetObjectAcl",
+                "s3:GetObject",
+                "s3:ListBucket",
+                "s3:DeleteObject",
+                "s3:PutObjectAcl"
+            ],
+            "Principal": {
+                "AWS": "arn:aws:iam::example-AWS-account-ID:user/example-user-name"
+            },
+            "Resource": [
+                "arn:aws:s3:::example-bucket-name/*",
+                "arn:aws:s3:::example-bucket-name"
+            ]
+        }
+    ]
+}
+```
+
+#### docker-compose
+
+Set the following values in your `.env` file.
+
+```
+PASSBOOK_POSTGRESQL__S3_BACKUP__ACCESS_KEY=
+PASSBOOK_POSTGRESQL__S3_BACKUP__SECRET_KEY=
+PASSBOOK_POSTGRESQL__S3_BACKUP__BUCKET=
+PASSBOOK_POSTGRESQL__S3_BACKUP__REGION=
+```
+
+If you want to backup to an S3-compatible server, like [minio](https://min.io/), use this setting:
+
+```
+PASSBOOK_POSTGRESQL__S3_BACKUP__HOST=http://play.min.io
+```
+
+#### Kubernetes
+
+Simply enable these options in your values.yaml file
+
+```yaml
+# Enable Database Backups to S3
+backup:
+    accessKey: access-key
+    secretKey: secret-key
+    bucket: s3-bucket
+    region: eu-central-1
+    host: s3-host
+```
+
+Afterwards, run a `helm upgrade` to update the ConfigMap. Backups are done automatically as above, at 00:00 every day.

website/docs/outposts/manual-deploy-docker-compose.md

@@ -0,0 +1,22 @@
+---
+title: Manual Outpost deployment in docker-compose
+---
+
+To deploy an outpost with docker-compose, use this snippet in your docker-compose file.
+
+You can also run the outpost in a separate docker-compose project, you just have to ensure that the outpost container can reach your application container.
+
+```yaml
+version: "3.5"
+
+services:
+    passbook_proxy:
+        image: beryju/passbook-proxy:0.10.0-stable
+        ports:
+            - 4180:4180
+            - 4443:4443
+        environment:
+            PASSBOOK_HOST: https://your-passbook.tld
+            PASSBOOK_INSECURE: "false"
+            PASSBOOK_TOKEN: token-generated-by-passbook
+```

website/docs/outposts/manual-deploy-kubernetes.md

@@ -0,0 +1,101 @@
+---
+title: Manual Outpost deployment on Kubernetes
+---
+
+Use the following manifest, replacing all values surrounded with `__`.
+
+Afterwards, configure the proxy provider to connect to `<service name>.<namespace>.svc.cluster.local`, and update your Ingress to connect to the `passbook-outpost` service.
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+    labels:
+        app.kubernetes.io/instance: test
+        app.kubernetes.io/managed-by: passbook.beryju.org
+        app.kubernetes.io/name: passbook-proxy
+        app.kubernetes.io/version: 0.10.0
+    name: passbook-outpost-api
+stringData:
+    passbook_host: "__PASSBOOK_URL__"
+    passbook_host_insecure: "true"
+    token: "__PASSBOOK_TOKEN__"
+type: Opaque
+---
+apiVersion: v1
+kind: Service
+metadata:
+    labels:
+        app.kubernetes.io/instance: test
+        app.kubernetes.io/managed-by: passbook.beryju.org
+        app.kubernetes.io/name: passbook-proxy
+        app.kubernetes.io/version: 0.10.0
+    name: passbook-outpost
+spec:
+    ports:
+        - name: http
+          port: 4180
+          protocol: TCP
+          targetPort: http
+        - name: https
+          port: 4443
+          protocol: TCP
+          targetPort: https
+    selector:
+        app.kubernetes.io/instance: test
+        app.kubernetes.io/managed-by: passbook.beryju.org
+        app.kubernetes.io/name: passbook-proxy
+        app.kubernetes.io/version: 0.10.0
+    type: ClusterIP
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+    labels:
+        app.kubernetes.io/instance: test
+        app.kubernetes.io/managed-by: passbook.beryju.org
+        app.kubernetes.io/name: passbook-proxy
+        app.kubernetes.io/version: 0.10.0
+    name: passbook-outpost
+spec:
+    selector:
+        matchLabels:
+            app.kubernetes.io/instance: test
+            app.kubernetes.io/managed-by: passbook.beryju.org
+            app.kubernetes.io/name: passbook-proxy
+            app.kubernetes.io/version: 0.10.0
+    template:
+        metadata:
+            labels:
+                app.kubernetes.io/instance: test
+                app.kubernetes.io/managed-by: passbook.beryju.org
+                app.kubernetes.io/name: passbook-proxy
+                app.kubernetes.io/version: 0.10.0
+        spec:
+            containers:
+                - env:
+                      - name: PASSBOOK_HOST
+                        valueFrom:
+                            secretKeyRef:
+                                key: passbook_host
+                                name: passbook-outpost-api
+                      - name: PASSBOOK_TOKEN
+                        valueFrom:
+                            secretKeyRef:
+                                key: token
+                                name: passbook-outpost-api
+                      - name: PASSBOOK_INSECURE
+                        valueFrom:
+                            secretKeyRef:
+                                key: passbook_host_insecure
+                                name: passbook-outpost-api
+                  image: beryju/passbook-proxy:0.10.0-stable
+                  name: proxy
+                  ports:
+                      - containerPort: 4180
+                        name: http
+                        protocol: TCP
+                      - containerPort: 4443
+                        name: https
+                        protocol: TCP
+```

website/docs/outposts/outposts.md

@@ -0,0 +1,21 @@
+---
+title: Outposts
+---
+
+An outpost is a single deployment of a passbook component, which can be deployed in a completely separate environment. Currently, only the Proxy Provider is supported as outpost.
+
+![](outposts.png)
+
+Upon creation, a service account and a token is generated. The service account only has permissions to read the outpost and provider configuration. This token is used by the Outpost to connect to passbook.
+
+passbook can manage the deployment, updating and general lifecycle of an Outpost. To communicate with the underlying platforms on which the outpost is deployed, passbook has "Service Connections".
+
+-   If you've deployed passbook on docker-compose, passbook automatically create a Service Connection for the local docker socket.
+-   If you've deployed passbook on Kubernetes, with `kubernetesIntegration` set to true (default), passbook automatically creates a Service Connection for the local Kubernetes Cluster.
+
+To deploy an outpost with these service connections, simply selected them during the creation of an Outpost. A background task is started, which creates the container/deployment. You can see that Status on the System Tasks page.
+
+To deploy an outpost manually, see:
+
+-   [Kubernetes](./manual-deploy-kubernetes.md)
+-   [docker-compose](./manual-deploy-docker-compose.md)

website/docs/outposts/upgrading.md

@@ -0,0 +1,11 @@
+---
+title: Upgrading an Outpost
+---
+
+In the Outpost Overview list, you'll see if any deployed outposts are out of date.
+
+![](./upgrading_outdated.png)
+
+To upgrade the Outpost to the latest version, simple adjust the docker tag of the outpost the the new version.
+
+Since the configuration is managed by passbook, that's all you have to do.

website/docs/policies/expression.md

@@ -0,0 +1,44 @@
+---
+title: Expression Policies
+---
+
+:::note
+These variables are available in addition to the common variables/functions defined in [**Expressions**](../expressions/index.md)
+:::
+
+The passing of the policy is determined by the return value of the code. Use `return True` to pass a policy and `return False` to fail it.
+
+### Available Functions
+
+#### `pb_message(message: str)`
+
+Add a message, visible by the end user. This can be used to show the reason why they were denied.
+
+Example:
+
+```python
+pb_message("Access denied")
+return False
+```
+
+### Context variables
+
+-   `request`: A PolicyRequest object, which has the following properties:
+    -   `request.user`: The current user, against which the policy is applied. ([ref](../expressions/reference/user-object.md))
+    -   `request.http_request`: The Django HTTP Request. ([ref](https://docs.djangoproject.com/en/3.0/ref/request-response/#httprequest-objects))
+    -   `request.obj`: A Django Model instance. This is only set if the policy is ran against an object.
+    -   `request.context`: A dictionary with dynamic data. This depends on the origin of the execution.
+-   `pb_is_sso_flow`: Boolean which is true if request was initiated by authenticating through an external provider.
+-   `pb_client_ip`: Client's IP Address or 255.255.255.255 if no IP Address could be extracted. Can be [compared](../expressions/index.md#comparing-ip-addresses), for example
+
+    ```python
+    return pb_client_ip in ip_network('10.0.0.0/24')
+    ```
+
+Additionally, when the policy is executed from a flow, every variable from the flow's current context is accessible under the `context` object.
+
+This includes the following:
+
+-   `prompt_data`: Data which has been saved from a prompt stage or an external source.
+-   `application`: The application the user is in the process of authorizing.
+-   `pending_user`: The currently pending user

website/docs/policies/index.md

@@ -0,0 +1,40 @@
+---
+title: Policies
+---
+
+## Standard Policies
+
+---
+
+### Reputation Policy
+
+passbook keeps track of failed login attempts by source IP and attempted username. These values are saved as scores. Each failed login decreases the score for the client IP as well as the targeted username by 1 (one).
+
+This policy can be used, for example, to prompt clients with a low score to pass a captcha before they can continue.
+
+## Expression Policy
+
+See [Expression Policy](expression.md).
+
+## Password Policies
+
+---
+
+### Password Policy
+
+This policy allows you to specify password rules, such as length and required characters.
+The following rules can be set:
+
+-   Minimum amount of uppercase characters.
+-   Minimum amount of lowercase characters.
+-   Minimum amount of symbols characters.
+-   Minimum length.
+-   Symbol charset (define which characters are counted as symbols).
+
+### Have I Been Pwned Policy
+
+This policy checks the hashed password against the [Have I Been Pwned](https://haveibeenpwned.com/) API. This only sends the first 5 characters of the hashed password. The remaining comparison is done within passbook.
+
+### Password-Expiry Policy
+
+This policy can enforce regular password rotation by expiring set passwords after a finite amount of time. This forces users to set a new password.

website/docs/property-mappings/expression.md

@@ -0,0 +1,15 @@
+---
+title: Property Mapping Expressions
+---
+
+The property mapping should return a value that is expected by the Provider/Source. Supported types are documented in the individual Provider/Source. Returning `None` is always accepted and would simply skip the mapping for which `None` was returned.
+
+:::note
+These variables are available in addition to the common variables/functions defined in [**Expressions**](../expressions/index.md)
+:::
+
+### Context Variables
+
+-   `user`: The current user. This may be `None` if there is no contextual user. ([ref](../expressions/reference/user-object.md))
+-   `request`: The current request. This may be `None` if there is no contextual request. ([ref](https://docs.djangoproject.com/en/3.0/ref/request-response/#httprequest-objects))
+-   Other arbitrary arguments given by the provider, this is documented on the Provider/Source.

website/docs/property-mappings/index.md

@@ -0,0 +1,25 @@
+---
+title: Property Mappings
+---
+
+Property Mappings allow you to pass information to external applications. For example, pass the current user's groups as a SAML parameter. Property Mappings are also used to map Source fields to passbook fields, for example when using LDAP.
+
+## SAML Property Mapping
+
+SAML Property Mappings allow you embed information into the SAML AuthN request. This information can then be used by the application to, for example, assign permissions to the object.
+
+## LDAP Property Mapping
+
+LDAP Property Mappings are used when you define a LDAP Source. These mappings define which LDAP property maps to which passbook property. By default, the following mappings are created:
+
+-   Autogenerated LDAP Mapping: givenName -> first_name
+-   Autogenerated LDAP Mapping: mail -> email
+-   Autogenerated LDAP Mapping: name -> name
+-   Autogenerated LDAP Mapping: sAMAccountName -> username
+-   Autogenerated LDAP Mapping: sn -> last_name
+
+These are configured with most common LDAP setups.
+
+## Scope Mapping
+
+Scope Mappings are used by the OAuth2 Provider to map information from passbook to OAuth2/OpenID Claims.

website/docs/providers/oauth2.md

@@ -0,0 +1,32 @@
+---
+title: OAuth2 Provider
+---
+
+This provider supports both generic OAuth2 as well as OpenID Connect
+
+Scopes can be configured using Scope Mappings, a type of [Property Mappings](../property-mappings/index.md#scope-mapping).
+
+| Endpoint             | URL                                                                  |
+| -------------------- | -------------------------------------------------------------------- |
+| Authorization        | `/application/o/authorize/`                                          |
+| Token                | `/application/o/token/`                                              |
+| User Info            | `/application/o/userinfo/`                                           |
+| End Session          | `/application/o/end-session/`                                        |
+| Introspect           | `/application/o/end-session/`                                        |
+| JWKS                 | `/application/o/<application slug>/jwks/`                            |
+| OpenID Configuration | `/application/o/<application slug>/.well-known/openid-configuration` |
+
+## GitHub Compatibility
+
+This provider also exposes a GitHub-compatible endpoint. This endpoint can be used by applications, which support authenticating against GitHub Enterprise, but not generic OpenID Connect.
+
+To use any of the GitHub Compatibility scopes, you have to use the GitHub Compatibility Endpoints.
+
+| Endpoint        | URL                         |
+| --------------- | --------------------------- |
+| Authorization   | `/login/oauth/authorize`    |
+| Token           | `/login/oauth/access_token` |
+| User Info       | `/user`                     |
+| User Teams Info | `/user/teams`               |
+
+To access the user's email address, a scope of `user:email` is required. To access their groups, `read:org` is required. Because these scopes are handled by a different endpoint, they are not customisable as a Scope Mapping.

website/docs/providers/proxy.md

@@ -0,0 +1,27 @@
+---
+title: Proxy Provider
+---
+
+:::info
+This provider is to be used in conjunction with [Outposts](../outposts/outposts.md)
+:::
+
+This provider protects applications, which have no built-in support for OAuth2 or SAML. This is done by running a lightweight Reverse Proxy in front of the application, which authenticates the requests.
+
+passbook Proxy is based on [oauth2_proxy](https://github.com/oauth2-proxy/oauth2-proxy), but has been integrated more tightly with passbook.
+
+The Proxy these extra headers to the application:
+
+| Header Name                    | Value                                               |
+| ------------------------------ | --------------------------------------------------- |
+| X-Forwarded-User               | The user's unique identifier (**not the username**) |
+| X-Forwarded-Email              | The user's email address                            |
+| X-Forwarded-Preferred-Username | The user's username                                 |
+| X-Auth-Username                | The user's username                                 |
+
+Additionally, you can add more custom headers using `additionalHeaders` in the User or Group Properties, for example
+
+```yaml
+additionalHeaders:
+    X-additional-header: bar
+```

website/docs/providers/saml.md

@@ -0,0 +1,13 @@
+---
+title: SAML Provider
+---
+
+This provider allows you to integrate enterprise software using the SAML2 Protocol. It supports signed requests and uses [Property Mappings](../property-mappings/index.md#saml-property-mapping) to determine which fields are exposed and what values they return. This makes it possible to expose vendor-specific fields.
+Default fields are exposed through auto-generated Property Mappings, which are prefixed with "Autogenerated".
+
+| Endpoint               | URL                                                          |
+| ---------------------- | ------------------------------------------------------------ |
+| SSO (Redirect binding) | `/application/saml/<application slug>/sso/binding/redirect/` |
+| SSO (POST binding)     | `/application/saml/<application slug>/sso/binding/post/`     |
+| IdP-initiated login    | `/application/saml/<application slug>/sso/binding/init/`     |
+| Metadata Download      | `/application/saml/<application slug>/metadata/`             |

website/docs/sources.md

@@ -0,0 +1,41 @@
+---
+title: Sources
+---
+
+Sources allow you to connect passbook to an existing user directory. They can also be used for social logins, using external providers such as Facebook, Twitter, etc.
+
+## Generic OAuth Source
+
+**All Integration-specific Sources are documented in the Integrations Section**
+
+This source allows users to enroll themselves with an external OAuth-based Identity Provider. The generic provider expects the endpoint to return OpenID-Connect compatible information. Vendor-specific implementations have their own OAuth Source.
+
+-   Policies: Allow/Forbid users from linking their accounts with this provider.
+-   Request Token URL: This field is used for OAuth v1 implementations and will be provided by the provider.
+-   Authorization URL: This value will be provided by the provider.
+-   Access Token URL: This value will be provided by the provider.
+-   Profile URL: This URL is called by passbook to retrieve user information upon successful authentication.
+-   Consumer key/Consumer secret: These values will be provided by the provider.
+
+## SAML Source
+
+This source allows passbook to act as a SAML Service Provider. Just like the SAML Provider, it supports signed requests. Vendor-specific documentation can be found in the Integrations Section.
+
+## LDAP Source
+
+This source allows you to import users and groups from an LDAP Server.
+
+-   Server URI: URI to your LDAP server/Domain Controller.
+-   Bind CN: CN of the bind user. This can also be a UPN in the format of `user@domain.tld`.
+-   Bind password: Password used during the bind process.
+-   Enable StartTLS: Enables StartTLS functionality. To use LDAPS instead, use port `636`.
+-   Base DN: Base DN used for all LDAP queries.
+-   Addition User DN: Prepended to the base DN for user queries.
+-   Addition Group DN: Prepended to the base DN for group queries.
+-   User object filter: Consider objects matching this filter to be users.
+-   Group object filter: Consider objects matching this filter to be groups.
+-   User group membership field: This field contains the user's group memberships.
+-   Object uniqueness field: This field contains a unique identifier.
+-   Sync groups: Enable/disable group synchronization. Groups are synced in the background every 5 minutes.
+-   Sync parent group: Optionally set this group as the parent group for all synced groups. An example use case of this would be to import Active Directory groups under a root `imported-from-ad` group.
+-   Property mappings: Define which LDAP properties map to which passbook properties. The default set of property mappings is generated for Active Directory. See also [LDAP Property Mappings](property-mappings/index.md#ldap-property-mapping)

website/docs/terminology.md

@@ -0,0 +1,32 @@
+---
+id: terminology
+title: Terminology
+---
+
+### Policy
+
+At a base level a policy is a yes/no gate. It will either evaluate to True or False depending on the Policy Kind and settings. For example, a "Group Membership Policy" evaluates to True if the user is member of the specified Group and False if not. This can be used to conditionally apply Stages, grant/deny access to various objects, and for other custom logic.
+
+### Provider
+
+A Provider is a way for other applications to authenticate against passbook. Common Providers are OpenID Connect (OIDC) and SAML.
+
+### Source
+
+Sources are locations from which users can be added to passbook. For example, an LDAP Connection to import Users from Active Directory, or an OAuth2 Connection to allow Social Logins.
+
+### Application
+
+An application links together Policies with a Provider, allowing you to control access. It also holds Information like UI Name, Icon and more.
+
+### Stages
+
+A stage represents a single verification or logic step. They are used to authenticate users, enroll users, and more. These stages can optionally be applied to a flow via policies.
+
+### Flows
+
+Flows are an ordered sequence of stages. These flows can be used to define how a user authenticates, enrolls, etc.
+
+### Property Mappings
+
+Property Mappings allow you to make information available for external applications. For example, if you want to login to AWS with passbook, you'd use Property Mappings to set the user's roles in AWS based on their group memberships in passbook.

website/docs/troubleshooting/access.md

@@ -0,0 +1,13 @@
+---
+title: Troubleshooting access problems
+---
+
+### I get an access denied error when trying to access an application.
+
+If your user is a superuser, or has the attribute `passbook_user_debug` set to true:
+
+![](./passbook_user_debug.png)
+
+Afterwards, try to access the application again. You will now see a message explaining which policy denied you access:
+
+![](./access_denied_message.png)

website/docs/upgrading/to-0.10.md

@@ -0,0 +1,75 @@
+---
+title: Upgrading to 0.10
+---
+
+This update brings a lot of big features, such as:
+
+-   New OAuth2/OpenID Provider
+
+    This new provider merges both OAuth2 and OpenID. It is based on the codebase of the old provider, which has been simplified and cleaned from the ground up. Support for Property Mappings has also been added. Because of this change, OpenID and OAuth2 Providers will have to be re-created.
+
+-   Proxy Provider
+
+    Due to this new OAuth2 Provider, the Application Gateway Provider, now simply called "Proxy Provider" has been revamped as well. The new passbook Proxy integrates more tightly with passbook via the new Outposts system. The new proxy also supports multiple applications per proxy instance, can configure TLS based on passbook Keypairs, and more.
+
+    See [Proxy](../providers/proxy.md)
+
+-   Outpost System
+
+    This is a new Object type, currently used only by the Proxy Provider. It manages the creation and permissions of service accounts, which are used by the outposts to communicate with passbook.
+
+    See [Outposts](../outposts/outposts.md)
+
+-   Flow Import/Export
+
+    Flows can now be imported and exported. This feature can be used as a backup system, or to share complex flows with other people. Example flows have also been added to the documentation to help you get going with passbook.
+
+## Under the hood
+
+-   passbook now runs on Django 3.1 and Channels with complete ASGI enabled
+-   uwsgi has been replaced with Gunicorn and uvicorn
+-   Elastic APM has been replaced with Sentry Performance metrics
+-   Flow title is now configurable separately from the name
+-   All logging output is now json
+
+## Upgrading
+
+### docker-compose
+
+The docker-compose file has been updated, please download the latest from `https://raw.githubusercontent.com/BeryJu/passbook/master/docker-compose.yml`.
+By default, the new compose file uses a fixed version to prevent unintended updates.
+
+Before updating the file, stop all containers. Then download the file, pull the new containers and start the database.
+
+```
+docker-compose down
+docker-compose pull
+docker-compose up --no-start
+docker-compose start redis postgrseql
+docker-compose run --rm server migrate
+docker-compose up -d
+```
+
+### Helm
+
+A few options have changed:
+
+-   `error_reporting` was changed from a simple boolean to a dictionary:
+
+```yaml
+error_reporting:
+    enabled: false
+    environment: customer
+    send_pii: false
+```
+
+-   The `apm` and `monitoring` blocks have been removed.
+-   `serverReplicas` and `workerReplicas` have been added
+
+### Upgrading
+
+This upgrade only applies if you are upgrading from a running 0.9 instance. Passbook detects this on startup, and automatically executes this upgrade.
+
+Because this upgrade brings the new OAuth2 Provider, the old providers will be lost in the process. Make sure to take note of the providers you want to bring over.
+
+Another side-effect of this upgrade is the change of OAuth2 URLs, see [here](../providers/oauth2.md).

website/docs/upgrading/to-0.11.md

@@ -0,0 +1,24 @@
+---
+title: Upgrading to 0.11
+---
+
+This update brings these headline features:
+
+-   Add Backup and Restore, currently only externally schedulable, documented [here](../maintenance/backups/index.md)
+-   New Admin Dashboard with more metrics and Charts
+
+    Shows successful and failed logins from the last 24 hours, as well as the most used applications
+
+-   Add search to all table views
+-   Outpost now supports a Docker Controller, which installs the Outpost on the same host as passbook, updates and manages it
+-   Add Token Identifier
+
+    Tokens now have an identifier which is used to reference to them, so the Primary key is not shown in URLs
+
+-   `core/applications/list` API now shows applications the user has access to via policies
+
+## Upgrading
+
+This upgrade can be done as with minor upgrades, the only external change is the new docker-compose file, which enabled the Docker Integration for Outposts. To use this feature, please download the latest docker-compose from [here](https://raw.githubusercontent.com/BeryJu/passbook/master/docker-compose.yml).
+
+Afterwards, you can simply run `docker-compose up -d` and then the normal upgrade command of `docker-compose run --rm server migrate`.

website/docs/upgrading/to-0.12.md

@@ -0,0 +1,65 @@
+---
+title: Upgrading to 0.12
+---
+
+This update brings these headline features:
+
+-   Rewrite Outpost state Logic, which now supports multiple concurrent Outpost instances.
+-   Add Kubernetes Integration for Outposts, which deploys and maintains Outposts with High Availability in a Kubernetes Cluster
+-   Add System Task Overview to see all background tasks, their status, the log output, and retry them
+-   Alerts now disappear automatically
+-   Audit Logs are now searchable
+-   Users can now create their own Tokens to access the API
+-   docker-compose deployment now uses traefik 2.3
+
+Fixes:
+
+-   Fix high CPU Usage of the proxy when Websocket connections fail
+
+## Upgrading
+
+### docker-compose
+
+Docker-compose users should download the latest docker-compose file from [here](https://raw.githubusercontent.com/BeryJu/passbook/master/docker-compose.yml). This includes the new traefik 2.3.
+
+Afterwards, you can simply run `docker-compose up -d` and then the normal upgrade command of `docker-compose run --rm server migrate`.
+
+### Kubernetes
+
+For Kubernetes users, there are some changes to the helm values.
+
+The values change from
+
+```yaml
+config:
+    # Optionally specify fixed secret_key, otherwise generated automatically
+    # secret_key: _k*@6h2u2@q-dku57hhgzb7tnx*ba9wodcb^s9g0j59@=y(@_o
+    # Enable error reporting
+    error_reporting:
+        enabled: false
+        environment: customer
+        send_pii: false
+    # Log level used by web and worker
+    # Can be either debug, info, warning, error
+    log_level: warning
+```
+
+to
+
+```yaml
+config:
+    # Optionally specify fixed secret_key, otherwise generated automatically
+    # secretKey: _k*@6h2u2@q-dku57hhgzb7tnx*ba9wodcb^s9g0j59@=y(@_o
+    # Enable error reporting
+    errorReporting:
+        enabled: false
+        environment: customer
+        sendPii: false
+    # Log level used by web and worker
+    # Can be either debug, info, warning, error
+    logLevel: warning
+```
+
+in order to be consistent with the rest of the settings.
+
+There is also a new setting called `kubernetesIntegration`, which controls the Kubernetes integration for passbook. When enabled (the default), a Service Account is created, which allows passbook to deploy and update Outposts.

website/docs/upgrading/to-0.9.md

@@ -0,0 +1,39 @@
+---
+title: Upgrading to 0.9
+---
+
+Due to some database changes that had to be rather sooner than later, there is no possibility to directly upgrade. You must extract the data before hand and import it again. It is recommended to spin up a second instance of passbook to do this.
+
+To export data from your old instance, run this command:
+
+-   docker-compose
+
+```
+docker-compose exec server ./manage.py dumpdata -o /tmp/passbook_dump.json passbook_core.User passbook_core.Group passbook_crypto.CertificateKeyPair passbook_audit.Event otp_totp.totpdevice otp_static.staticdevice otp_static.statictoken
+docker cp passbook_server_1:/tmp/passbook_dump.json passbook_dump.json
+```
+
+-   kubernetes
+
+```
+kubectl exec -it passbook-web-... -- ./manage.py dumpdata -o /tmp/passbook_dump.json passbook_core.User passbook_core.Group passbook_crypto.CertificateKeyPair passbook_audit.Event otp_totp.totpdevice otp_static.staticdevice otp_static.statictoken
+kubectl cp passbook-web-...:/tmp/passbook_dump.json passbook_dump.json
+```
+
+After that, create a new passbook instance in a different namespace (kubernetes) or in a different folder (docker-compose). Once this instance is running, you can use the following commands to restore the data. On docker-compose, you still have to run the `migrate` command, to create all database structures.
+
+-   docker-compose
+
+```
+docker cp passbook_dump.json new_passbook_server_1:/tmp/passbook_dump.json
+docker-compose exec server ./manage.py loaddata /tmp/passbook_dump.json
+```
+
+-   kubernetes
+
+```
+kubectl cp passbook_dump.json passbook-web-...:/tmp/passbook_dump.json
+kubectl exec -it passbook-web-... -- ./manage.py loaddata /tmp/passbook_dump.json
+```
+
+Now, you should be able to login to the new passbook instance, and migrate the rest of the data over.