-
-
Notifications
You must be signed in to change notification settings - Fork 907
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LDAP not working, Invalid credentials #2743
Comments
Hi! I have had more successful results using the following flow: Look at the documentation for LDAP providers, the allowed stages are Identification, Password and Authenticator validator . While in your flow I see a Login stage, this may be the source of your problem. |
Hello everyone! I finding my self with a similar problem. I tinkered with the flow but without success. Were you able to make this work? Only difference is I'm using the Kubernetes integration. Thank you! |
Same problem for me... Does anyone had success in resolving this issue yet? |
Problem reproducible here. |
Can you post the logs of both the ldap outpost, the authentik server itself, and also try with the default authentication flow? |
Can you post the logs of both the ldap outpost, the authentik server itself, and also try with the default authentication flow?
The logs of the outpost are already posted here. Setting the level to debug does not help, no more info is logged.
I am already using the default flow.
The Aurhentik server itself does not produce any log output when searching the LDAP.
Maybe a caching issue? I could try using direct bind and search.
|
When using the cached binding, restart the outpost, then you should get more logs |
I have the same problem, i tried many different Flow setups.
|
Same here... Edit: Somehow I needed to recreate the ldap outpost... |
Same problem here running on version 2023.2.2 inside Kubernetes.
The logs below are from the outpost ldap pod with debug on. I don't see any logs appear in the server/worker pods when triggering these.
EDIT: I've fixed my issue by adding another stage in my flow. I noticed the docs under the Create Custom Flow section only utilized two of the created stages with orders 10 and 30 (between steps 3 and 4). I added the |
我这里也有这个问题 server log {"auth_via": "unauthenticated", "event": "f(exec): Flow not applicable to current user", "exc": "FlowNonApplicableException()", "flow_slug": "ldap-authentication-flow", "host": "example.com:8012", "level": "warning", "logger": "authentik.flows.views.executor", "pid": 6278, "request_id": "3378dd964c47428fabbac97fc426289a", "timestamp": "2023-03-03T08:46:45.218857"}
{"auth_via": "unauthenticated", "errors": {"error_message": ["Not a valid string."]}, "event": "f(ch): Invalid challenge", "host": "example:8012", "level": "warning", "logger": "authentik.flows.stage", "pid": 6278, "request_id": "3378dd964c47428fabbac97fc426289a", "stage": null, "stage_view": "authentik.flows.stage.AccessDeniedChallengeView", "timestamp": "2023-03-03T08:46:45.220117"}
{"auth_via": "unauthenticated", "event": "/api/v3/flows/executor/ldap-authentication-flow/?query=goauthentik.io%252Foutpost%252Fldap%3Dtrue", "host": "example.com:8012", "level": "info", "logger": "authentik.asgi", "method": "GET", "pid": 6278, "remote": "10.196.220.254", "request_id": "3378dd964c47428fabbac97fc426289a", "runtime": 17, "scheme": "http", "status": 200, "timestamp": "2023-03-03T08:46:45.226641", "user": "", "user_agent": "goauthentik.io/outpost/2023.2.2"} |
I had the same issue. The only way I found to fix it is using direct binding/querying. |
i'm using a flow i created from the cooptonian youtube video that has the identification stage and and password stage just as the image showed in this thread.. it was working for a while and stopped. the restarting of the ldap docker outpost didn't help... creating the user, outpost, and everything LDAP related did work but a couple days later everythign stopped working agian... and i can confirm its not a cache issue as it doesn't work on direct connection either. |
I managed to get it to work with these settings: Please let me know if this works for you, especially the notes marked as important. authentik version Important Pay special attention to the Authentik LDAP Provider's Direct Binding. Thank you @Zapfmeister LDAPBind User: Important Note how the group Base DN: Connection is set to SSL (port 636) (you may need to specify AuthentikFlowFlow settings
Stage Bindings
Both set to:
Identification Stage
Password Stage
Authentication Stage
ProviderYour provider must be associated with an application and selected in the LDAP outpost.
Important I have a search group set, |
Produced the error: What fixed it for me, was to change the provider from cached binding and cached querying to direct. |
FIXED (sort of): My so-called Turns out it did not liked it (I guess 'it' is the main authentik server, looking at the log below and the HTTP 302s there). Hence I switched to an https version of the endpoint, using the url on the advanced setting in the LDAP application edit page, and the ldapsearch query worked. The problem is that the URL that authentik showed me is the public one and I would like to keep the communication between the ldap outpost and the authentik server inside the docker network, for example, using Using the internal name of docker it does not work tho. Suggestions are welcome. authentik 2024.2.1 Same configuration (if im not wrong) as TMUniversal's setup (above) and it does not work for me. Executing from another container inside the same network of the ldap outpost, authentik and authentik's worker:
My outpost container tells me:
My authentik container tells me:
I dont know if worth mentioning: I "checked access" of the application LDAP against |
Any news? |
Hello there!
I tried to get the LDAP Outpost in Authentik working, but i'm always getting an
Invalid credentials
error. I don't know what to do now.I created an LDAP Providar, Application and Outpost, as you can see on the screenshots.
And also a custom flow, because i read that LDAP is not working if a flow has MFA enabled.
But when i try to do a
ldapsearch
i'm getting the following error:In the
ak-outpost-ldap
container created by Authentik i get the following log:{"bindDN":"cn=***,ou=users,dc=ldap,dc=***,dc=***","client":"192.***.***.***","event":"Bind request","level":"info","requestId":"5e90557b-5942-4001-b2dd-fa4453798bac","timestamp":"2022-04-18T07:34:28Z","took-ms":35479}
I'm using the latest Authentik version
2022.4.1
and deployed everything withdocker-compose
.Do you have an idea what the problem is here?
Greetings
The text was updated successfully, but these errors were encountered: