Open StizLor opened 4 months ago
I am also having trouble authenticating over LDAP. It is not exactly the same setup, but I think it is close enough.
My problem is that LDAP authentication is not working for the only account that has MFA. Everyone else can authenticate at Jellyfin using LDAP no problem.
Is this a known issue?
@DirgoSalga Do you use the default authentication flow for the ldap provider (default-authentication-flow)? I assume by your comment that you also use authentik as ldap provider. If you do, the flow contains a mfa stage that is run if a mfa-device is enrolled.
Testing it myself, the logs show that the flow fails at the mfa stage. I do not know if it is intended that way. If you have no session when authenticating on jellyfin via ldap, a redirect would be needed to enter the mfa. When already authenticated, authentik does not seem pass the mfa stage correctly.
Either this is a bug and needs to be fixed or you could write a policy or whole new flow. The policy would just skip the mfa. The flow wouldn't include a mfa stage.
No satisfactory solution but at least all flows would work again and apps could still authenticate.
Thanks for your reply! I will give the workaround a try as soon as I find some time to tinker around again. I'll let you know if I get it working.
i'm also running into this with a custom flow without mfa testing the flow in authentik seems to work fine without mfa but ldapsearch says insufficient permissions
hmmm interestingly enough if i put it on direct querying, i get operations error but with cached i can see in the logs it shows up as an anonymous user if i chance objectclass to 'username' rather than user i do get "success" but i see no info with direct querying
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I have not found a solution yet
Describe the bug Issue revolves around ldap provider via outpost and binding ldap. When setting a group or user other than the ldap-bind (user or group) the ldap can't bind to authentik anymore. This is tested with jellyfin as ldap client application. In Short -
The ldap bind is successful when:
The ldap bind fails when:
To Reproduce Steps to reproduce the behavior:
Config in Jellyfin: https://docs.goauthentik.io/integrations/services/jellyfin/
Expected behavior It is expected that the bind is always working, no matter what groups/users are bound to the application.
Screenshots
Logs
when failing
Authentik Events:
Jellyfin Logs:
Outpost Logs:
Authentik Worker:
Version and Deployment (please complete the following information):