Every LDAP account should have access to XMPP #140
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Remove the filtered role from the ejabberd config
Follow-up to #123
This has revealed a flaw in the new directory structure. If we remove the filtering altogether, LDAP read-only accounts for the wiki and xmpp become valid XMPP accounts.
Right now my solution is to turn these accounts from a
personto aorganizationalPerson. Then the filter would look like this (aperson, but not anorganizationalPerson). In LDAP anorganizationalPersonis also apersonsince it's "subclassing" it.The ACIs will also need to be updated to add the
objectClassattribute to the list of allowed attributes for the read-only account, because they are not part of the list for nowSo why are they a "Person" in the first place? They're not people (also not "organizational people"), so shouldn't they be something else?
I found a good solution. LDAP accounts used to filter users will be moved be under
cn=applications,dc=kosmos,dc=org, for example theuid=xmpp,ou=kosmos.org,cn=applications,dc=kosmos,dc=orgaccount. Then everything undercn=users,dc=kosmos,dc=orgare actual users/peopleACIs need to be set on the Organizational Units to allow the applications accounts to perform the searches
Closing this one now that ejabberd has been upgraded and restarted yesterday. The config change in #141 had not been applied, this has been fixed in #142