-
Notifications
You must be signed in to change notification settings - Fork 184
Enabling TLS generates exception when attempting login #737
Comments
Hi @nerdalertdk, Unfortunately I'm not well-versed with FreeIPA - but I'll do my best to help you out. On the server that hosts your web application, have you inserted your TLS certificate as instructed here?: https://www.freeipa.org/page/HowTo/LDAP#Tool_configuration
This was required for me using ActiveDirectory to be able to connect via TLS with a server that is not connected to the domain - but required access to our AD server via TLS. |
Tls works fine when the site have access to the ldap server, as soon as it looses connection (think vpn) I get the exception. It should fall over to use Laravel database as Auth When I set tls=false in the .env the site works but the log gets spammed with exception on every page view |
Oh okay I understand now, thanks for clarifying. This is a bug, I'm able to reproduce this, fix is coming out shortly! |
Greate, one last question when the site don't have ldap access can we stop the error spam in the log :)
|
Done! 😄 Connection exceptions will now only be sent to the log when logging is enabled. |
Released v6.0.6 with these changes. Thanks! |
Description:
When fallback is
true
and the site have not connection to ldap I get this errorSite works fine in fallover mode with no TLS
Steps To Reproduce:
Add this to you
.env
fileFirst login where the site have an LDAP connection (to sync user)
then block ldap connection and login will fail
The text was updated successfully, but these errors were encountered: