diff --git a/website/developer-docs/setup/full-dev-environment.md b/website/developer-docs/setup/full-dev-environment.md
index 40f16d72b..e1dcc6810 100644
--- a/website/developer-docs/setup/full-dev-environment.md
+++ b/website/developer-docs/setup/full-dev-environment.md
@@ -18,15 +18,19 @@ You can also use a native install, if you prefer.
 
 ## Backend Setup
 
+:::info
+Depending on your platform, some native dependencies might be required. On macOS, run `brew install libxmlsec1 libpq`, and for the CLI tools `brew install postgresql redis node@20`
+:::
+
+:::info
+As long as [this issue](https://github.com/xmlsec/python-xmlsec/issues/252) is open, a workaround is required to install a compatible version of `libxmlsec1` with brew, see [this comment](https://github.com/xmlsec/python-xmlsec/issues/254#issuecomment-1511135314).
+:::
+
 ```shell
 poetry shell # Creates a python virtualenv, and activates it in a new shell
 poetry install # Install all required dependencies, including development dependencies
 ```
 
-:::info
-Depending on platform, some native dependencies might be required. On macOS, run `brew install libxmlsec1 libpq`, and for the CLI tools `brew install postgresql redis node@20`
-:::
-
 To configure authentik to use the local databases, we need a local config file. This file can be generated by running `make gen-dev-config`.
 
 To apply database migrations, run `make migrate`. This is needed after the initial setup, and whenever you fetch new source from upstream.