-
Notifications
You must be signed in to change notification settings - Fork 127
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 Login Issue #283
Comments
+1 |
Got it to work eventually myself as well, beware |
How did you get it to work? What backend are you using for LDAP? Would you be able to post your configuration? I'm hoping it can help me track down my issues. |
Here's my working config for v2:
Since
Although, to be perfectly honest with you, I don't like the interface of this project at all - it is too complicated for the casual users; I will probably go back to a custom patched wg-easy with an external authenticator. Here is the patch to wg-easy to support the @WolfgangsChannel Managed to pull it off. It's rather simple actually. The changes are as follows:
This patch has the effect that the headers sent by Authelia always contain the I am a bit amazed by the lack of proper options in this area of WireGuard frontend, but I always keep looking since the protocol in itself is SO GOOD compared to anything else I have used. |
I'm having issues with wg-portal and lldap as a LDAPS authentication provider.
When opening the front end, I see this error:
If I try to sign in with any of the LDAP accounts, an authentication error occurs.
Here's the snag, LDAPS binds properly. I can see on the lldap side the request come through, bind and return the correct users based on the sync filter. I've pulled the database file to see if the user information was synced. Looks like everything came over except password, but I'm assuming that's the correct behavior. For reference, the same LDAP backend is working fine with other services.
On first run with a new database file I see this in the wg-portal log. It continues to cycle starting to synchronize, and fetching the raw users endlessly. It's also not in alignment to the synchronization interval.
My docker compose file:
My config,yml
I'm unsure if this issue is a configuration issue on my end or an issue with how LDAP synchronization occurs behind the scenes.
I took a quick look at user_manager.go, but based on the flow I would think that the users are synced properly. Not sure why I see the backend connection error when it appears to have been set up properly.
Any thoughts or suggestions as to the source of my issues?
The text was updated successfully, but these errors were encountered: