Replies: 1 comment
-
Is the use case unclear? Or does nobody else has this (or similar) requirement for enclosed? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've successfully setup Enclosed with docker compose (great documentation by the way 👍) and Traefik, and after playing around it works like expected.
What I wanted to achieve next is putting Enclosed behind Traefik authentication middleware, so that only authenticated users (from IDP) are able to create notes and that these notes can be read without authentication needed (anonymously).
The problem is however, even when I add bypass middleware for Traefik, anonymous users will still be able to navigate to the page to create new notes (as this doesn't seem to dispatch a new request but more like an URL rewrite; fyi I'm not very familiar with modern web applications). Still, when an anonymous users tries to create a note it will fail subsequently, as it will now create an underlying request to
https://notes.example.com/api/notes
which gets intercepted by Traefik correctly, resulting in a302
redirect (to the authentication) and leading to a CORS error in the console.TLDR
When adding authentication middleware in the reverse proxy, anonymous users are currently not able to create new notes but they are still able to navigate to this page (which I'm trying to prevent).
I'm not sure if this is currently possible with the current version of the application but any bit of help would be appreciated.
Setup
.env
compose.yaml
Beta Was this translation helpful? Give feedback.
All reactions