-
Notifications
You must be signed in to change notification settings - Fork 38
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
TypeError: 'NoneType' object is not callable for result.user_groups #57
Comments
Ah looks like the form is making some assumptions about the return type, which could potentially have flask-ldap3-login/flask_ldap3_login/__init__.py Lines 398 to 400 in 3cf0faf
Should be a relatively simply fix to the forms code, will try raise a fix later today. |
The problem above also occurs for me. I have isolated the problem to the _save_user decorator not registering. This means the _save_user function stays None and this causes the NoneType error. Any suggestion on how to make sure the _save_user decorator gets loaded? EDIT: |
Looks like this is the exact problem - the stack trace above looks like a red-herring to me on second glance. @ciobancai does the above solution solve your problem? I will assume so and close this issue, but if not please re-open. |
Also, just a side note: after a long internal debate, I have made the difficult decision that I will no longer be actively maintaining this repo. I am now in the process of finding a new maintainer - if this is something that may interest you, you can find more details in the README |
Hi, I have a flask project configured with multiple blueprints and we are working to integrate the project with this module. We are receiving the below error
Below is the configuration for ldap
# Ldap
LDAP_HOST = 'ldap-host'
LDAP_BASE_DN = 'dc=com'
LDAP_USER_DN = 'ou=People'
LDAP_GROUP_DN = 'ou=Groups'
LDAP_BIND_USER_DN = 'secret'
LDAP_BIND_USER_PASSWORD = 'secret'
LDAP_USE_SSL = True
LDAP_PORT = 636
LDAP_GROUP_OBJECT_FILTER = '(objectclass=groupOfUniqueNames)'
LDAP_GROUP_SEARCH_SCOPE = 'SUBTREE'
From the logs we can see the user is authenticated but for some reason the group is empty, is there any way to ignore this ?
The text was updated successfully, but these errors were encountered: