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

Exchanging ldap3 constants in if/else #175

Merged
merged 3 commits into from
Aug 20, 2020
Merged

Conversation

1kastner
Copy link
Contributor

They were just the wrong way round and no error has popped up so far, see the ldap3 author's statements at cannatag/ldap3#855

@1kastner 1kastner changed the title Exchanging ldap3 constants in if/else [WIP] Exchanging ldap3 constants in if/else Aug 18, 2020
@1kastner 1kastner changed the title [WIP] Exchanging ldap3 constants in if/else Exchanging ldap3 constants in if/else Aug 18, 2020
@1kastner
Copy link
Contributor Author

@manics I hope everything is solved. I believe use_ssl means either SSL or STARTTLS is used, right? Unencrypted communication is not supported at all, is it?

@1kastner
Copy link
Contributor Author

PS: For me the solution is working in application and the tests pass, I don't know how many more test cases are needed here.

Copy link
Member

@manics manics left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this! The fix makes sense to me

@dhirschfeld would you mind giving a 👍 since you're more familiar with the code? Thanks!

@manics manics requested a review from dhirschfeld August 20, 2020 11:35
Copy link
Collaborator

@dhirschfeld dhirschfeld left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dhirschfeld
Copy link
Collaborator

I haven't looked at this code in a long time but the description in the linked issue seems pretty clear.

:shipit:

@manics manics merged commit 7092125 into jupyterhub:master Aug 20, 2020
@1kastner 1kastner deleted the patch-1 branch August 21, 2020 06:24
@1kastner
Copy link
Contributor Author

A small question @manics, how will things continue from here? How does the versioning work?

According to what I see at https://github.com/jupyterhub/ldapauthenticator the pypi version is at 1.3.1 (including my quick fix from #172), the conda version at 1.3.0 (without the fix, so I guess it should break if you install it freshly), and the last github release is from 1.2.2 (so completely out of date, see https://github.com/jupyterhub/ldapauthenticator/releases).

This new proper fix now is on the dev branch for the new version 1.3.2. When might the version 1.3.2 be released? And through which channels? Thank you very much!

@manics
Copy link
Member

manics commented Aug 28, 2020

I've just tagged 1.3.2 so it should be on pypi soon.

In general conda-forge packages are maintained independently of the Python/Pypi package: https://github.com/conda-forge/jupyterhub-ldapauthenticator-feedstock

Though in this case some of the maintainers overlap

@1kastner
Copy link
Contributor Author

@manics so the github releases (see https://github.com/jupyterhub/ldapauthenticator/releases ) are not used anymore?

@dhirschfeld
Copy link
Collaborator

GitHub "releases" are just some UI sugar on top of an ordinary git tag and don't add anything required for packaging. By default conda-forge builds from the pypi sources.

All the tags can be seen in the tags view: https://github.com/jupyterhub/ldapauthenticator/tags

@1kastner
Copy link
Contributor Author

Thank you very much for that information!

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

Successfully merging this pull request may close these issues.

3 participants