-
Notifications
You must be signed in to change notification settings - Fork 13
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
LDAP-Group mappings works only with proper Unix-Groups #2
Comments
How do users look like with their default groups? Specifically, how do you think we can change that group query to make it configurable and allow to specify other queries other than the posix approach? I would love to have it customizable but LDAP is just so customizable that it's hard to test all scenarios. |
Well, that is the problem. There is no default group for a user. In the AD / GOSA (RFC2307Bis) schema you don't have those. I'm currently taking a deeper look into the plugin. It seems that it need to be restructured a little bit in order to account for these different setup. |
I am also eyeing this plugin, but it does not work for me with AD implementation of LDAP. I use some php software with good LDAP/AD integration, namely Nextcloud's user_ldap module. Perhaps one could look at the solution hints there? I like LDAP integrations where I can:
I wish you devs strength and luck to integrate grav with AD 😄. I would be glad to do any testing. |
Yes, That is usually the way how the whole ldap-authentication works.
I've done some work to get the plugin to work with rfc2307bis type LDAP trees. The branch is not yet read for a PR For those who want to try it out, there are some config differences I had to add jpegPhoto to blacklist Fields. Grav can't handle the base64 image data... But that's another issue... |
grav-plugin-login-ldap/login-ldap.php
Line 176 in a5656aa
I had a look at the plugin's code. And the line above suggest that the user's groups can only be found if the user is a member of an "objectClass=posixGroup" group.
In my environment I have 'virtual' groups which do not have the gidNumber. Such groups can be found in GoSa and ActiveDirectory allow these kind of groups.
Here's an example of such a group:
The text was updated successfully, but these errors were encountered: