diff --git a/backend/capellacollab/core/authentication/exceptions.py b/backend/capellacollab/core/authentication/exceptions.py
index 3daa73dff..5ff97250a 100644
--- a/backend/capellacollab/core/authentication/exceptions.py
+++ b/backend/capellacollab/core/authentication/exceptions.py
@@ -53,7 +53,7 @@ def __init__(self, scheme: str):
             title="Invalid scheme detected",
             reason=(
                 f"The scheme '{scheme}' is not supported. "
-                "Use 'basic' or 'bearer' instead"
+                "Authentication is only supported via cookies or basic authentication."
             ),
             err_code="UNKNOWN_SCHEME",
         )
diff --git a/docs/docs/development/backend/authentication.md b/docs/docs/development/backend/authentication.md
deleted file mode 100644
index 4d74c1877..000000000
--- a/docs/docs/development/backend/authentication.md
+++ /dev/null
@@ -1,71 +0,0 @@
-<!--
- ~ SPDX-FileCopyrightText: Copyright DB InfraGO AG and contributors
- ~ SPDX-License-Identifier: Apache-2.0
- -->
-
-The are two ways to authenticate against the backend in a development
-environment. The first is to use a personal access token (PAT) and the second
-is to use a bearer token.
-
-## Personal Access Tokens
-
-!!! note
-
-    To create a personal access token you need a running frontend.
-
-Find more information about authentication with personal access tokens in the
-user documentation: [Authentication](../../api/index.md)
-
-## Bearer Token
-
-Request the `auth_url`
-
-```sh
-curl -X 'GET' \
-  'http://127.0.0.1:8000/api/v1/authentication/' \
-  -H 'accept: application/json'
-```
-
-Opening the `auth_url` in a browser leads you to a "Mock OAuth2 Server Sign-in"
-page.
-
-Login as user `admin` to be redirected to a page that is reachable when the
-frontend runs. Anyway the redirect URL in the browser's address input field
-contains two parameters `code` and `status`.
-
-Example:
-
-<pre>
-    http://localhost:4200/oauth2/callback?...
-    ...code=<span style="color:green">MREy4raZT9JqaYn_50yJraU4zkclGQbNcbudW404ekc</span>...
-    ...&state=<span style="color:green">r7huaqqdDBWTb8x4gUDIpt36izM0Au</span>
-</pre>
-
-One must copy these parameters and post them via a second request returning an
-access token:
-
-```sh
-curl -X 'POST' \
-  'http://127.0.0.1:8000/api/v1/authentication/tokens' \
-  -H 'accept: application/json' \
-  -H 'Content-Type: application/json' \
-  -d '{
-  "code": "MREy4raZT9JqaYn_50yJraU4zkclGQbNcbudW404ekc",
-  "state": "r7huaqqdDBWTb8x4gUDIpt36izM0Au"
-}'
-```
-
-To send a request using that token you may want to request the list of
-projects:
-
-```sh
-curl -X 'GET' \
-  'http://127.0.0.1:8000/api/v1/projects/' \
-  -H 'accept: application/json' \
-  -H 'Authorization: Bearer <TOKEN>'
-```
-
-whereby `<TOKEN>` must be replaced by the token you received above.
-
-Using the Swagger UI one can click on the lock symbols to enter the access
-token.