Jens L.

Docker should by default use the system's resolver (via a proxy that resolves the container names), and authentik doesn't overwrite that behaviour. You can exec into the container and use...

@sam-brownlow your issue is unrelated; the 400 bad request in your case is caused by docker-compose (note the hyphen, docker space compose doesn't have this issue) giving containers names with...

> @BeryJu Care to explain why this has been closed? Was eagerly waiting for this :( I was just renaming some branches for cleanup, I forgot that closes the PR...

The way domain-level authentication works, this can't be implemented currently. The outpost is go and the core is python, and authorization is only done during the authentication of the user....

The outpost checks if the request has a valid auth cookie, if not redirects the user to the core for a full OAuth flow, where the authentication and authorization happens,...

in a world where the entire backend is Go, this would still happen similarly, except the outpost would talk directly to the core via GRPC/etc to do additional checks, and...

I was also able to reproduce this on a Mi 9T Pro, no idea what is causing this though

I've been meaning to add support for this using some sort of separate like `|` or `;`, have not gotten around to it yet since I want to do some...

The LDAP schema of the outpost is roughly based on [RFC-2307Bis](https://ldapwiki.com/wiki/RFC2307Schema). A user's groups are listed as `memberOf` attribute which contains the full DN to the group. Groups contain a...

set `AUTHENTIK_INSECURE` to `"true"` to accept any certificate