LDAP - session length? #7192
Replies: 3 comments 8 replies
-
Please note this response was created using generative AI leveraging previously available information from the repository. This information may be helpful however it is our strong recommendation that you carefully consider the information before blindly applying it. Based on the information provided in the sources, there is no specific mention of an idle timeout setting directly within Authelia or LLDAP that would address the issue you're experiencing with binding times. However, there are a few considerations and configurations that might help optimize the performance:
If you continue to experience issues, it might be beneficial to look into more detailed logs from both Authelia and LLDAP to identify any specific bottlenecks or errors that could be contributing to the long bind times. This comment was generated by Glime. |
Beta Was this translation helpful? Give feedback.
-
So we don't do any pooling currently as there wasn't a clear benefit due to the frequency of connections made. We can experiment with one if you're interested in giving feedback. |
Beta Was this translation helpful? Give feedback.
-
I have this running successfully since several weeks. Was just tying up
some lose ends and wanted to submit some of my code to LLDAP once you guys
have released yours.
…On Mon, Jun 10, 2024, 03:25 James Elliott ***@***.***> wrote:
Hey sorry I didn't see this, if you enable trace logs it should indicate
the pooling. As far as the release it's likely in 4.39
—
Reply to this email directly, view it on GitHub
<#7192 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6CUVLDDGZ6EHM666LCOI3ZGUFAXAVCNFSM6AAAAABGKLNG22VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TOMRSGMYDC>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
"Binding" in (L)LDAP takes a significant time, probably due to the hashing algorithm / password verification. On a low powered device, this can be 2500ms, followed by one or two queries in the 1-2ms range. So I wonder, is there an idle timeout I have missed in Authelia or LLDAP. Are sessions actually pooled/re-used?
Am I missing something else here? LLDAP is just another container on the same host, exclusively used by Authelia.
Beta Was this translation helpful? Give feedback.
All reactions