Christian Albrecht

@d-schiffner @BeryJu could it be that this comparison https://github.com/goauthentik/authentik/blob/60c88370822d28637d61170dd4edc148e0ade681/internal/outpost/ldap/bind/memory/memory.go#L58 needs the same refactoring as that comparison https://github.com/goauthentik/authentik/blob/7cedc840b07ae7d974f9dc7abe93e41dca6c46ea/internal/outpost/ldap/search/memory/memory.go#L78 which was added in https://github.com/goauthentik/authentik/pull/6096 Although i do not speak go, i can...

While this was happening for a dovecot service user and therefore affecting all users wanting to authenticate their Mailclient, it now happened for a specific human user again. On the...

No, that does not fix the cached authentication failure after the flow execution failure.

Naa, happened again. This was stupid anyway, because if the "failed to execute flow" event is triggered, the direct binder returns `LDAPResultInvalidCredentials` instead of the `LDAPResultOperationsError`, which i somehow assumed...

And finally that one https://github.com/mayflower/authentik/commit/7e11c4f38223cca155054e29a57735f1846ff0f0 fixed it together with the previous commits.