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

Extend instruction hints regarding importance of use of sAMAccountName for users to groups #38

Open
mblandi opened this issue Aug 12, 2020 · 0 comments

Comments

@mblandi
Copy link

mblandi commented Aug 12, 2020

The clue to why my 4.3.X plone groups panel was returning unusable encoded names from ActiveDirectory was within your description of why the objectguid cannot be used for user id attribute.

You might add a note in the installation instructions that this is also important for groups: to also use sAMAccountName to hook those up properly in plone. Took a lot of web searches for me to find the missing step.

This was tricky to resolve, because ZMI (and getGroups() from the lower acl_users level) presents the group names fine even using objectguid vs. the encoded problem in plone. A quick change to groupid_attr in Plone Active Directory plugin properties seems to have fixed it up.

I guess it also doesn't help that the user id attribute is configured separately from the group id attribute in ZMI, but the controls are there.

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

No branches or pull requests

1 participant