search

nilsteampassnet / TeamPass

Collaborative Passwords Manager
https://www.teampass.net
1.67k stars 545 forks source link

[3.0.0.2] LDAP is not working #2831

Open reginfo opened 3 years ago

reginfo commented 3 years ago
### Steps to reproduce 1.Login to Admin 2. Try to setup LDAP ### Expected behaviour Setting saves ### Actual behavior After page refresh or page changing, setting are not saved. Also is there all fields? On v2.7 there is field "LDAP domain controller(s)" where we specify LDAP servers. ### Server configuration **Operating system**: Ubuntu 18.04 **Web server:** Apache/2.4.29 **Database:** mariadb Ver 15.1 Distrib 10.1.47-MariaDB **PHP version:** PHP 7.2.24 **Teampass version:** 3.0.0.2 **Updated from an older Teampass or fresh install:** Fresh Install ### Client configuration **Browser:** EDGE **Operating system:** Windows 10 20H2
benodilo commented 3 years ago

Hello, Same problem on 3.0.0.7 ? Don't work on port 389 or 636 with AD. On the same server that's work fine with older version 2.X Best regards.

turekg commented 3 years ago

Hello, Same problem on 3.0.0.7 ? Don't work on port 389 or 636 with AD. On the same server that's work fine with older version 2.X Best regards.

It's just hasn't been implemented. If you look at the 3.X branch(s) you will see that the LDAP folder is not there

benodilo commented 3 years ago

Hello, Same problem on 3.0.0.7 ? Don't work on port 389 or 636 with AD. On the same server that's work fine with older version 2.X Best regards.

It's just hasn't been implemented. If you look at the 3.X branch(s) you will see that the LDAP folder is not there

ok thks for reply !

ckatterl commented 3 years ago

You mean, that LDAP-Authenticatioin is not yet implemented in 3.0.0.7? As per release-info, it should be? I am too stuck in the "Can't connect-issue"....

ckatterl commented 3 years ago

Tried version 3.0.0.8 now. The "can't connect" issue is gone. but the gear is rotating and does not stop. checking with tcpdump, i cannot see any traffic on the ldap-ports.

f0ssie commented 3 years ago

I've also tried version 3.0.0.7 today, a completely fresh installation, but I also got the "Error: -1 - Can't contact LDAP server" error message. No matter what I enter in the Hosts field, tcpdump shows that the server always tries to connect to 127.0.0.1:

15:42:26.527850 IP 127.0.0.1.52084 > 127.0.0.1.389: Flags [S], seq 2934674681, win 65495, options [mss 65495,sackOK,TS val 2878634823 ecr 0,nop,wscale 7], length 0
15:42:26.527869 IP 127.0.0.1.389 > 127.0.0.1.52084: Flags [R.], seq 0, ack 2934674682, win 0, length 0
ckatterl commented 3 years ago

The current version 3.0.0.8 produces ldap-queries against the server now (checked with tcpdump). However, using the ldap-test I get an error:

Error : 49 Invalid credentials. AcceptSecurityContext error, data 52e, v4563.

Normally, this means, that the password isn't correct, but the username is.

I tried to use a username, which does not exist. Then, there's no error message but the circle is rotating saying "in progress". Using a correct username but wrong password immediately throws the above error - same as with correct password.

Any advice?

BR, Christian

AtlanteDeveloppement commented 3 years ago

Hello Same problem with 3.0.0.8 ldap with active directory doesn't work Error : 49 Invalid credentials. AcceptSecurityContext error, data 52e, v4563. Thanks

jdolny commented 3 years ago

Same here. LDAP not working in 3.0.0.8 AcceptSecurityContext error, data 52e, v4563.

pablojrc commented 3 years ago

HI! I have the same situation in a CentOS 7.9 PHP 7.4 MariaDB TeamPass 3.0.0.8 imagen

byalcin23 commented 2 years ago

I have a similar issue with TeamPass 3.0.0.8. image

jim-ccit commented 2 years ago

Still broken in 3.0.0.9, exactly the same issues and results as above.

sergey2786 commented 2 years ago

Version 3.0.17 no connect to ldap( Error 500 in nginx. If so, what is the solution to this problem? image

jvalters commented 2 years ago

Hello,

The same issue is there any solution? Still the same issues. Could you please @nilsteampassnet check or maybe you have some workaround?

Thanks.

LaiaRos commented 1 year ago

Hello,

Still the same issue with Ubuntu 22.04 and TeamPass 3.0.0.22. Every test remains "In progress" eternally. Has anyone managed to work with ldap?

Thanks.

sfoglema commented 1 year ago

So I went through the process of upgrading from 2.1.26 to 3.0.0.22. This upgrade already had AD LDAP working and still works on 3.0.0.22. However, the LDAP screen shows no information that LDAP is setup. The tp.config.php file does show my LDAP settings. We do occasionally get the "in progress" issue, but refreshing and logging in again seems to fix it. Overall, there are several minor issues, but way better than being on LastPass. My setup is on CentOS7 (I know, I need to migrate soon), PHP 8 and TeamPass 3.0.0.22

sfoglema commented 1 year ago

It now appears that my AD LDAP config is NOT working, but instead your most recent password was simply saved in Teampass. As soon as anyone changes their AD password, they cannot connect to TeamPass unless they use their OLD password.

Any update on getting LDAP integration working with TeamPass 3.0.0.22?

Thanks.

jvalters commented 1 year ago

It now appears that my AD LDAP config is NOT working, but instead your most recent password was simply saved in Teampass. As soon as anyone changes their AD password, they cannot connect to TeamPass unless they use their OLD password.

Any update on getting LDAP integration working with TeamPass 3.0.0.22?

Thanks.

We're still waiting for the group filter to be added by @nilsteampassnet and I think this is also a good use case that on each login it synces with LDAP

alozano-sct commented 1 year ago

Hi, i have same problem with OpenLdap and migration from 2.17.xx When i configured LDAP and test in the same page, i can see logs on my ldap server and the test its ok. But when i try to login, always obtained user or password is incorrect.

And on Users table, LDAP Syncronization, do not anything.

And ldap.debug.txt dont have any information, its really frustrating T_T

ismaelvillalba commented 1 year ago

Hello, has a solution been found for the error? I am experiencing an issue where I can correctly configure LDAP with my Active Directory, and it successfully finds the user when searching. However, when I try to synchronize LDAP with TeamPass for user login, none of the users load. There are no error messages, it just says "done" but it doesn't work correctly.

tp1 tp2 tp3 tp4

nilsteampassnet commented 1 year ago

@ismaelvillalba Please update to latest commit. I have passed some fixes regarding AD.

ismaelvillalba commented 1 year ago

@nilsteampassnet I updated the version to TeamPass 3.0.10 successfully and configured the server from 0 again, but I still have the same problem. In the LDAP configuration I can correctly test the users but when I want to synchronize them it appears as "Done", and it does not load anything.