You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have multi-factor authentication configured with our LDAP provider. This ldapauthentcator plugin works perfectly out of the box for me except for the fact that it results in two separate MFA push notifications to the user for every login.
Then, right after that in authenticate(), conn.bind() is called again which triggers another DUO push.
Just as a test, I modified the logic that sets auto_bind to:
auto_bind=ldap3.AUTO_BIND_NONE
And it worked with only a single MFA push.
I'd like to avoid the double-push, but I'm not really sure of the implications of changing the auto_bind logic for other users of this library. I may submit a PR at some point.
We have multi-factor authentication configured with our LDAP provider. This
ldapauthentcator
plugin works perfectly out of the box for me except for the fact that it results in two separate MFA push notifications to the user for every login.Specifically, I found that
ldapauthenticator.py->authenticate()
, callget_connection()
which in turn callsldap3.Connection()
withauto_bind
set. So,bind()
is called which triggers an MFA push to the user.Then, right after that in
authenticate()
,conn.bind()
is called again which triggers another DUO push.Just as a test, I modified the logic that sets
auto_bind
to:And it worked with only a single MFA push.
I'd like to avoid the double-push, but I'm not really sure of the implications of changing the auto_bind logic for other users of this library. I may submit a PR at some point.
My environment:
Versions:
the-littlest-jupyterhub configuration file with redactions:
The text was updated successfully, but these errors were encountered: