Skip to content
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

[4] LDAP -Could not set value "60" for option "network_timeout". #35316

Closed
PhilETaylor opened this issue Aug 23, 2021 Discussed in #35312 · 19 comments
Closed

[4] LDAP -Could not set value "60" for option "network_timeout". #35316

PhilETaylor opened this issue Aug 23, 2021 Discussed in #35312 · 19 comments

Comments

@PhilETaylor
Copy link
Contributor

Discussed in #35312

Originally posted by nickdring August 23, 2021
Hi there,
I migrated a 3.10 to the 4.0 that was finally released last week.
All good so far apart from an issue I'm having with LDAP login.
I'm using the standard LDAP plugin, there is no third party stuff on the site whatsoever.
On the same test site with J3 login via ldap worked fine but with the exact same settings new user and existing users are not able to log in.
The logs don't show anything but on the actual front end I see this error:
0 Could not set value "60" for option "network_timeout".
Attached is a screen shot showing the ldap settings.
https://www.dropbox.com/s/whnzuahaywwfqli/ldap.png

@PhilETaylor

This comment was marked as abuse.

@nickdring
Copy link

HI there, activated debut but it didn't make any difference as you can see here: https://www.dropbox.com/s/zth93wohxde9ncc/Screenshot.png?dl=0
default_socket_timeout is set to 60

@nickdring
Copy link

@PhilETaylor

This comment was marked as abuse.

@nickdring
Copy link

Hi Phil, yep front or back, new or existing user.

@PhilETaylor

This comment was marked as abuse.

@PhilETaylor

This comment was marked as abuse.

@PhilETaylor

This comment was marked as abuse.

@nickdring
Copy link

Hi there, here you go https://www.dropbox.com/s/zw64id5wsbnj81b/systeminfo.txt

@PhilETaylor

This comment was marked as abuse.

@nickdring
Copy link

HI so I removed the ldaps:// as you suggested and now there is another error: 2021-08-24T09:22:25+00:00 INFO 10.255.7.56 ldapfailure Username and password do not match or you do not have an account yet.
I asked my IT department and there reply was that if we removed LDAPS how does Joomla know that we require an LDAPS connection?

@PhilETaylor

This comment was marked as abuse.

@nickdring
Copy link

nickdring commented Aug 24, 2021

We don't use TLS we use ldaps.
From experience I think the Joomla reply 'Username and password do not match or you do not have an account yet' is the standard reply that Joomla sends back when there is an error, whatever the problem is.
Personally I would think it might be an idea to allow people to specify ldap or ldaps.
We've tried a few different options but so far we havent managed to get it to work.

@PhilETaylor

This comment was marked as abuse.

@PhilETaylor

This comment was marked as abuse.

@nickdring
Copy link

Hi we have around 70 sites running J3 which have been using this setup for quite a few years. The certificate is self signed on a local domain.

@PhilETaylor

This comment was marked as abuse.

@nickdring
Copy link

No worries Phil, we aren’t looking to move quite yet to J4 but I’d be happy to test the plug-in when you’ve added support for LDAPS.
Nick

@nickdring
Copy link

I updated to 4.0.2 but the issue still remains so I guess its hasn't been looked at yet. Just to say I'm quite happy to test the new plugin when it arrives. I guess this hasn't been noticed as most people who use Joomla don't use LDAP for authentication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants