Closed alexdongli0829 closed 2 months ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
@alexdongli0829 The expected behavior you mention is incorrect. According to the README (as of writing, at least), the expected behavior is to use StartTLS with set to False, and normal SSL when set to True. However, I do find it slightly problematic, that disabling TLS entirely is not possible. That is not the subject matter here though.
Bug description
I tried to use ldapauthenticator to connect to openldap server, as my server has no ssl and I want to connect it to 389, so I set it this parameter to False according to README(https://github.com/jupyterhub/ldapauthenticator)
However, I keep facing the SSL issue from ldap3:
Expected behaviour
If I set the use_ssl to False, it will not use SSL, otherwise, it will use SSL
Actual behaviour
According to the source code:
It looks like if I set False, it will use AUTO_BIND_TLS_BEFORE_BIND but if I set True, it will be AUTO_BIND_NO_TLS with no TLS? Whats the logic here? I think its wrong, I believe it should be:
Do I make any mistake or misunderstanding about the document and code? If yes, could we make the document more clearly?
How to reproduce
its on all the OS with ldapauthenticator 1.3.2